[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9964b317d8a1487d9dcd3fb53d7e8d1c@BY2PR03MB299.namprd03.prod.outlook.com>
Date: Wed, 2 Apr 2014 06:25:39 +0000
From: KY Srinivasan <kys@...rosoft.com>
To: KY Srinivasan <kys@...rosoft.com>,
"x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"olaf@...fle.de" <olaf@...fle.de>,
"apw@...onical.com" <apw@...onical.com>,
"jasowang@...hat.com" <jasowang@...hat.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"hpa@...or.com" <hpa@...or.com>
Subject: RE: [PATCH 1/1] x86: irq: Handle VMBUS driver being a module
Thomas,
With the Hyper-V irq cleanup that you checked in, currently Hyper-V interrupts are not being displayed when
Hyper-V is configured as a module. This patch fixes the issue.
Regards,
K. Y
> -----Original Message-----
> From: K. Y. Srinivasan [mailto:kys@...rosoft.com]
> Sent: Tuesday, April 1, 2014 11:52 PM
> To: x86@...nel.org; linux-kernel@...r.kernel.org; olaf@...fle.de;
> apw@...onical.com; jasowang@...hat.com; tglx@...utronix.de;
> hpa@...or.com
> Cc: KY Srinivasan
> Subject: [PATCH 1/1] x86: irq: Handle VMBUS driver being a module
>
> Hyper-V VMBUS driver can be a module; handle this case correctly. Please
> apply.
>
> Signed-off-by: K. Y. Srinivasan <kys@...rosoft.com>
> ---
> arch/x86/kernel/irq.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/x86/kernel/irq.c b/arch/x86/kernel/irq.c
> index 42805fa..283a76a 100644
> --- a/arch/x86/kernel/irq.c
> +++ b/arch/x86/kernel/irq.c
> @@ -125,7 +125,7 @@ int arch_show_interrupts(struct seq_file *p, int prec)
> seq_printf(p, "%10u ", per_cpu(mce_poll_count, j));
> seq_printf(p, " Machine check polls\n");
> #endif
> -#if defined(CONFIG_HYPERV) || defined(CONFIG_XEN)
> +#if IS_ENABLED(CONFIG_HYPERV) || defined(CONFIG_XEN)
> seq_printf(p, "%*s: ", prec, "THR");
> for_each_online_cpu(j)
> seq_printf(p, "%10u ", irq_stats(j)->irq_hv_callback_count);
> --
> 1.7.4.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists