[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53da10fbf2904c6597568abdf10fe8f0@SN2PR03MB061.namprd03.prod.outlook.com>
Date: Wed, 13 Feb 2013 03:58:46 +0000
From: KY Srinivasan <kys@...rosoft.com>
To: "H. Peter Anvin" <hpa@...or.com>
CC: Yinghai Lu <yinghai@...nel.org>,
"mingo@...nel.org" <mingo@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"hpa@...ux.intel.com" <hpa@...ux.intel.com>,
"linux-tip-commits@...r.kernel.org"
<linux-tip-commits@...r.kernel.org>
Subject: RE: [tip:x86/hyperv] X86: Handle Hyper-V vmbus interrupts as
special hypervisor interrupts
> -----Original Message-----
> From: H. Peter Anvin [mailto:hpa@...or.com]
> Sent: Tuesday, February 12, 2013 10:55 PM
> To: KY Srinivasan
> Cc: Yinghai Lu; mingo@...nel.org; linux-kernel@...r.kernel.org;
> tglx@...utronix.de; hpa@...ux.intel.com; linux-tip-commits@...r.kernel.org
> Subject: Re: [tip:x86/hyperv] X86: Handle Hyper-V vmbus interrupts as special
> hypervisor interrupts
>
> On 02/12/2013 07:49 PM, KY Srinivasan wrote:
> >>>
> >>> The issue was that you could turn on CONFIG_HYPERV without enabling
> >>> CONFIG_X86_LOCAL_APIC. Peter fixed it.
> >>>
> >>
> >> He is asking why you are using IS_ENABLED() instead of #ifdef. The
> >> difference is that IS_ENABLED() works even for modules.
> >
> > My mistake!
> >
>
> Well, which one do you need?
I chose the IS_ENABLED() because I wanted to cover the case where HYPERV is configured as a module as well.
K. Y
>
> -hpa
>
>
> --
> H. Peter Anvin, Intel Open Source Technology Center
> I work for Intel. I don't speak on their behalf.
>
>
Powered by blists - more mailing lists