RE: [tip:x86/hyperv] X86: Handle Hyper-V vmbus interrupts as special hypervisor interrupts

2013-02-13 Thread KY Srinivasan
h...@linux.intel.com; linux-tip-comm...@vger.kernel.org > Subject: Re: [tip:x86/hyperv] X86: Handle Hyper-V vmbus interrupts as special > hypervisor interrupts > > On Tue, Feb 12, 2013 at 7:58 PM, KY Srinivasan wrote: > > > > > >> -Original Message- >

Re: [tip:x86/hyperv] X86: Handle Hyper-V vmbus interrupts as special hypervisor interrupts

2013-02-12 Thread Yinghai Lu
kernel.org; >> t...@linutronix.de; h...@linux.intel.com; linux-tip-comm...@vger.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: >> >&g

RE: [tip:x86/hyperv] X86: Handle Hyper-V vmbus interrupts as special hypervisor interrupts

2013-02-12 Thread KY Srinivasan
rnel.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 > >>> CONFI

Re: [tip:x86/hyperv] X86: Handle Hyper-V vmbus interrupts as special hypervisor interrupts

2013-02-12 Thread H. Peter Anvin
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!

RE: [tip:x86/hyperv] X86: Handle Hyper-V vmbus interrupts as special hypervisor interrupts

2013-02-12 Thread KY Srinivasan
rnel.org > Subject: Re: [tip:x86/hyperv] X86: Handle Hyper-V vmbus interrupts as special > hypervisor interrupts > > On 02/12/2013 07:32 PM, KY Srinivasan wrote: > >>> > >>> +#if IS_ENABLED(CONFIG_HYPERV) > >>> +apicinterrupt HYPERVISOR_CALLBACK_V

Re: [tip:x86/hyperv] X86: Handle Hyper-V vmbus interrupts as special hypervisor interrupts

2013-02-12 Thread H. Peter Anvin
On 02/12/2013 07:32 PM, KY Srinivasan wrote: +#if IS_ENABLED(CONFIG_HYPERV) +apicinterrupt HYPERVISOR_CALLBACK_VECTOR \ + hyperv_callback_vector hyperv_vector_handler +#endif /* CONFIG_HYPERV */ + so #ifdef CONFIG_HYPERV does not work here? The issue was that you could turn on CONFIG_H

RE: [tip:x86/hyperv] X86: Handle Hyper-V vmbus interrupts as special hypervisor interrupts

2013-02-12 Thread KY Srinivasan
nux.intel.com > Cc: linux-tip-comm...@vger.kernel.org > Subject: Re: [tip:x86/hyperv] X86: Handle Hyper-V vmbus interrupts as special > hypervisor interrupts > > On Tue, Feb 12, 2013 at 4:58 PM, tip-bot for K. Y. Srinivasan > wrote: > > Commit-ID: bc2b0331e077f5763

Re: [tip:x86/hyperv] X86: Handle Hyper-V vmbus interrupts as special hypervisor interrupts

2013-02-12 Thread Yinghai Lu
On Tue, Feb 12, 2013 at 4:58 PM, tip-bot for K. Y. Srinivasan wrote: > Commit-ID: bc2b0331e077f576369a2b6c75d15ed4de4ef91f > Gitweb: http://git.kernel.org/tip/bc2b0331e077f576369a2b6c75d15ed4de4ef91f > Author: K. Y. Srinivasan > AuthorDate: Sun, 3 Feb 2013 17:22:39 -0800 > Committer: H.

[tip:x86/hyperv] X86: Handle Hyper-V vmbus interrupts as special hypervisor interrupts

2013-02-12 Thread tip-bot for K. Y. Srinivasan
Commit-ID: bc2b0331e077f576369a2b6c75d15ed4de4ef91f Gitweb: http://git.kernel.org/tip/bc2b0331e077f576369a2b6c75d15ed4de4ef91f Author: K. Y. Srinivasan AuthorDate: Sun, 3 Feb 2013 17:22:39 -0800 Committer: H. Peter Anvin CommitDate: Tue, 12 Feb 2013 16:27:15 -0800 X86: Handle Hyper-V v