[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ed79f9e06117454aa6b01f425bb3f6cd@SN2PR03MB061.namprd03.prod.outlook.com>
Date: Wed, 23 Jan 2013 15:57:32 +0000
From: KY Srinivasan <kys@...rosoft.com>
To: "H. Peter Anvin" <hpa@...or.com>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
CC: Borislav Petkov <bp@...en8.de>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.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>,
Ingo Molnar <mingo@...nel.org>,
"jeremy@...p.org" <jeremy@...p.org>,
"Jan Beulich (JBeulich@...e.com)" <JBeulich@...e.com>
Subject: RE: [PATCH 1/1] X86: Handle Hyper-V vmbus interrupts as special
hypervisor interrupts
> -----Original Message-----
> From: H. Peter Anvin [mailto:hpa@...or.com]
> Sent: Tuesday, January 22, 2013 6:20 PM
> To: Konrad Rzeszutek Wilk; KY Srinivasan
> Cc: Borislav Petkov; gregkh@...uxfoundation.org; linux-kernel@...r.kernel.org;
> devel@...uxdriverproject.org; olaf@...fle.de; apw@...onical.com;
> jasowang@...hat.com; tglx@...utronix.de; Ingo Molnar; jeremy@...p.org; Jan
> Beulich (JBeulich@...e.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@...cle.com> wrote:
>
> >On Fri, Jan 18, 2013 at 03:27:33PM +0000, KY Srinivasan wrote:
> >>
> >>
> >> > -----Original Message-----
> >> > From: Borislav Petkov [mailto:bp@...en8.de]
> >> > Sent: Friday, January 18, 2013 8:11 AM
> >> > To: KY Srinivasan
> >> > Cc: gregkh@...uxfoundation.org; linux-kernel@...r.kernel.org;
> >> > devel@...uxdriverproject.org; olaf@...fle.de; apw@...onical.com;
> >> > jasowang@...hat.com; tglx@...utronix.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@...rosoft.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.
>
Powered by blists - more mailing lists