> -----Original Message----- > From: Borislav Petkov [mailto:bp@xxxxxxxxx] > Sent: Friday, January 18, 2013 8:11 AM > To: KY Srinivasan > Cc: gregkh@xxxxxxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; > devel@xxxxxxxxxxxxxxxxxxxxxx; olaf@xxxxxxxxx; apw@xxxxxxxxxxxxx; > jasowang@xxxxxxxxxx; tglx@xxxxxxxxxxxxx; 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@xxxxxxxxxxxxx> > > --- > > 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, K. Y > > -- > Regards/Gruss, > Boris. > > Sent from a fat crate under my desk. Formatting is fine. > -- > _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
