From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: x86@kernel.org, "Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>,
"Andrew Jones" <drjones@redhat.com>
Subject: Re: [PATCH] x86/irq: hide HYP in /proc/interrupts when not on Xen/Hyper-V
Date: Tue, 07 Jul 2015 14:40:50 +0200 [thread overview]
Message-ID: <87k2uc16p9.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <20150704082653.GA13934@gmail.com> (Ingo Molnar's message of "Sat, 4 Jul 2015 10:26:53 +0200")
Ingo Molnar <mingo@kernel.org> writes:
> * Vitaly Kuznetsov <vkuznets@redhat.com> wrote:
>
>> Hypervisor callback interrupts are only accounted on Xen/Hyper-V and we
>> detect hypervisor's type in early boot. There is no point in having
>> always-zero HYP: line on other hypervisors or bare metal.
>>
>> Suggested-by: Radim Krčmář <rkrcmar@redhat.com>
>> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
>> ---
>> arch/x86/kernel/irq.c | 13 +++++++++----
>> 1 file changed, 9 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/x86/kernel/irq.c b/arch/x86/kernel/irq.c
>> index 88b36648..0c82064 100644
>> --- a/arch/x86/kernel/irq.c
>> +++ b/arch/x86/kernel/irq.c
>> @@ -18,6 +18,7 @@
>> #include <asm/mce.h>
>> #include <asm/hw_irq.h>
>> #include <asm/desc.h>
>> +#include <asm/hypervisor.h>
>>
>> #define CREATE_TRACE_POINTS
>> #include <asm/trace/irq_vectors.h>
>> @@ -139,10 +140,14 @@ int arch_show_interrupts(struct seq_file *p, int prec)
>> seq_puts(p, " Machine check polls\n");
>> #endif
>> #if IS_ENABLED(CONFIG_HYPERV) || defined(CONFIG_XEN)
>> - seq_printf(p, "%*s: ", prec, "HYP");
>> - for_each_online_cpu(j)
>> - seq_printf(p, "%10u ", irq_stats(j)->irq_hv_callback_count);
>> - seq_puts(p, " Hypervisor callback interrupts\n");
>> + if (x86_hyper == &x86_hyper_ms_hyperv ||
>> + x86_hyper == &x86_hyper_xen) {
>> + seq_printf(p, "%*s: ", prec, "HYP");
>> + for_each_online_cpu(j)
>> + seq_printf(p, "%10u ",
>> + irq_stats(j)->irq_hv_callback_count);
>> + seq_puts(p, " Hypervisor callback interrupts\n");
>> + }
>
> So I think we should simplify this to:
>
> if (x86_hyper) {
> ...
> }
>
> this will print the HYP line on hypervisors that don't use
> HYPERVISOR_CALLBACK_VECTOR, but it will make it a lot more self-maintaining, we
> won't accidentally skip this line on hypervisors that start using the callback
> IRQ.
I was under an impression KVM and Vmware don't use these hypervisor
callback irqs 'by desing' and even if one day they start using it
someone will have to put inc_irq_stat() somewhere.
If the goal is to avoid having x86_hyper_ms_hyperv/x86_hyper_xen in
irq.c we can follow Andrew's suggestion and add a flag
(use_callback_irqs?) to struct hypervisor_x86.
Thanks,
--
Vitaly
next prev parent reply other threads:[~2015-07-07 12:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 11:27 Vitaly Kuznetsov
2015-07-04 8:26 ` Ingo Molnar
2015-07-06 13:57 ` Andrew Jones
2015-07-06 14:24 ` Andrew Jones
2015-07-06 15:02 ` Boris Ostrovsky
2015-07-07 12:40 ` Vitaly Kuznetsov [this message]
2015-07-07 12:54 ` Ingo Molnar
2015-07-07 13:45 ` Vitaly Kuznetsov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k2uc16p9.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=drjones@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome