[PATCH 1/1] X86: Handle Hyper-V vmbus interrupts as special hypervisor interrupts

KY Srinivasan kys at microsoft.com
Wed Jan 23 15:57:32 UTC 2013



> -----Original Message-----
> From: H. Peter Anvin [mailto:hpa at zytor.com]
> Sent: Tuesday, January 22, 2013 6:20 PM
> To: Konrad Rzeszutek Wilk; KY Srinivasan
> Cc: Borislav Petkov; gregkh at linuxfoundation.org; linux-kernel at vger.kernel.org;
> devel at linuxdriverproject.org; olaf at aepfle.de; apw at canonical.com;
> jasowang at redhat.com; tglx at linutronix.de; Ingo Molnar; jeremy at goop.org; Jan
> Beulich (JBeulich at suse.com)
> Subject: Re: [PATCH 1/1] X86: Handle Hyper-V vmbus interrupts as special
> hypervisor interrupts
> 
> Yes, how about we rename this the hypervisor vector...

Will do.

K. Y
> 
> Konrad Rzeszutek Wilk <konrad.wilk at oracle.com> wrote:
> 
> >On Fri, Jan 18, 2013 at 03:27:33PM +0000, KY Srinivasan wrote:
> >>
> >>
> >> > -----Original Message-----
> >> > From: Borislav Petkov [mailto:bp at alien8.de]
> >> > Sent: Friday, January 18, 2013 8:11 AM
> >> > To: KY Srinivasan
> >> > Cc: gregkh at linuxfoundation.org; linux-kernel at vger.kernel.org;
> >> > devel at linuxdriverproject.org; olaf at aepfle.de; apw at canonical.com;
> >> > jasowang at redhat.com; tglx at linutronix.de; H. Peter Anvin; Ingo
> >Molnar
> >> > Subject: Re: [PATCH 1/1] X86: Handle Hyper-V vmbus interrupts as
> >special
> >> > hypervisor interrupts
> >> >
> >> > On Thu, Jan 17, 2013 at 04:39:37PM -0800, K. Y. Srinivasan wrote:
> >> > >
> >> > > Signed-off-by: K. Y. Srinivasan <kys at microsoft.com>
> >> > > ---
> >> > >  arch/x86/include/asm/irq_vectors.h |    2 +
> >> > >  arch/x86/include/asm/mshyperv.h    |    4 +++
> >> > >  arch/x86/kernel/cpu/mshyperv.c     |   39
> >> > ++++++++++++++++++++++++++++++++++++
> >> > >  arch/x86/kernel/entry_32.S         |    7 ++++++
> >> > >  arch/x86/kernel/entry_64.S         |    5 ++++
> >> > >  5 files changed, 57 insertions(+), 0 deletions(-)
> >> > >
> >> > > diff --git a/arch/x86/include/asm/irq_vectors.h
> >> > b/arch/x86/include/asm/irq_vectors.h
> >> > > index 1508e51..c2ff239 100644
> >> > > --- a/arch/x86/include/asm/irq_vectors.h
> >> > > +++ b/arch/x86/include/asm/irq_vectors.h
> >> > > @@ -112,6 +112,8 @@
> >> > >  /* Xen vector callback to receive events in a HVM domain */
> >> > >  #define XEN_HVM_EVTCHN_CALLBACK		0xf3
> >> > >
> >> > > +/* Hyper-V vector callback to receive vmbus interrupts*/
> >> > > +#define HYPER_V_CALLBACK_VECTOR		0xf2
> >> >
> >> > Btw, could those hypervisor vectors be merged into one
> >VIRT_INTR_VECTOR
> >> > and be shared between the hypervisors? I mean, you can't have a xen
> >and
> >> > hyperv hypervisor running next to each other and fihgting over that
> >> > vector, right?
> >>
> >> You are right; we could just have one vector for this. Let me wait
> >for other comments and
> >> input from Xen maintainers before I make this change.
> >>
> >> Regards,
> >>
> >
> >Looks OK to me.
> >
> >> K. Y
> >> >
> >> > --
> >> > Regards/Gruss,
> >> >     Boris.
> >> >
> >> > Sent from a fat crate under my desk. Formatting is fine.
> >> > --
> >> >
> >>
> 
> --
> Sent from my Android phone with K-9 Mail. Please excuse my brevity.
> 



More information about the devel mailing list