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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2bd8c994-3e70-413b-85de-caec46428b1e@email.android.com>
Date:	Tue, 22 Jan 2013 17:19:37 -0600
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
	KY Srinivasan <kys@...rosoft.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

Yes, how about we rename this the hypervisor vector...

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/