mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	KY Srinivasan <kys@microsoft.com>
Cc: Borislav Petkov <bp@alien8.de>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	"olaf@aepfle.de" <olaf@aepfle.de>,
	"apw@canonical.com" <apw@canonical.com>,
	"jasowang@redhat.com" <jasowang@redhat.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>,
	"jeremy@goop.org" <jeremy@goop.org>,
	"Jan Beulich (JBeulich@suse.com)" <JBeulich@suse.com>
Subject: Re: [PATCH 1/1] X86: Handle Hyper-V vmbus interrupts as special hypervisor interrupts
Date: Tue, 22 Jan 2013 17:19:37 -0600	[thread overview]
Message-ID: <2bd8c994-3e70-413b-85de-caec46428b1e@email.android.com> (raw)
In-Reply-To: <20130122222056.GC14503@phenom.dumpdata.com>

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

Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:

>On Fri, Jan 18, 2013 at 03:27:33PM +0000, KY Srinivasan wrote:
>> 
>> 
>> > -----Original Message-----
>> > From: Borislav Petkov [mailto:bp@alien8.de]
>> > Sent: Friday, January 18, 2013 8:11 AM
>> > To: KY Srinivasan
>> > Cc: gregkh@linuxfoundation.org; linux-kernel@vger.kernel.org;
>> > devel@linuxdriverproject.org; olaf@aepfle.de; apw@canonical.com;
>> > jasowang@redhat.com; tglx@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@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.

  reply	other threads:[~2013-01-22 23:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18  0:39 K. Y. Srinivasan
2013-01-18  0:23 ` Greg KH
2013-01-18  1:07   ` KY Srinivasan
2013-01-18 13:10 ` Borislav Petkov
2013-01-18 15:27   ` KY Srinivasan
2013-01-22 22:20     ` Konrad Rzeszutek Wilk
2013-01-22 23:19       ` H. Peter Anvin [this message]
2013-01-23 15:37         ` Konrad Rzeszutek Wilk
2013-01-23 16:04           ` H. Peter Anvin
2013-01-23 16:10           ` KY Srinivasan
2013-01-23 15:57         ` KY Srinivasan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2bd8c994-3e70-413b-85de-caec46428b1e@email.android.com \
    --to=hpa@zytor.com \
    --cc=JBeulich@suse.com \
    --cc=apw@canonical.com \
    --cc=bp@alien8.de \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jasowang@redhat.com \
    --cc=jeremy@goop.org \
    --cc=konrad.wilk@oracle.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=olaf@aepfle.de \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®