From: KY Srinivasan <kys@microsoft.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "olaf@aepfle.de" <olaf@aepfle.de>, "bp@alien8.de" <bp@alien8.de>,
"apw@canonical.com" <apw@canonical.com>,
"x86@kernel.org" <x86@kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>
Subject: RE: [PATCH RESEND 1/1] X86: Handle Hyper-V vmbus interrupts as special hypervisor interrupts
Date: Thu, 24 Jan 2013 16:07:40 +0000 [thread overview]
Message-ID: <27092660926e4d3f80394697cc0dc858@SN2PR03MB061.namprd03.prod.outlook.com> (raw)
In-Reply-To: <5101035D02000078000B8FFD@nat28.tlf.novell.com>
> -----Original Message-----
> From: Jan Beulich [mailto:JBeulich@suse.com]
> Sent: Thursday, January 24, 2013 3:48 AM
> To: KY Srinivasan
> Cc: olaf@aepfle.de; bp@alien8.de; apw@canonical.com; x86@kernel.org;
> tglx@linutronix.de; devel@linuxdriverproject.org; gregkh@linuxfoundation.org;
> jasowang@redhat.com; linux-kernel@vger.kernel.org; hpa@zytor.com
> Subject: Re: [PATCH RESEND 1/1] X86: Handle Hyper-V vmbus interrupts as
> special hypervisor interrupts
>
> >>> On 24.01.13 at 02:17, "K. Y. Srinivasan" <kys@microsoft.com> wrote:
> > @@ -69,6 +74,11 @@ static void __init ms_hyperv_init_platform(void)
> > ms_hyperv.features, ms_hyperv.hints);
> >
> > clocksource_register_hz(&hyperv_cs, NSEC_PER_SEC/100);
> > +
> > + /*
> > + * Setup the IDT for hypervisor callback.
> > + */
> > + alloc_intr_gate(HYPERVISOR_CALLBACK_VECTOR,
> hyperv_callback_vector);
>
> Isn't doing this unconditionally here as problematic as the call to
> clocksource_register_hz() turned out to be when Xen's Hyper-V
> shim reacts to the CPUID inquiry above?
I was not sure what to make this conditional on at run-time. To the extent
that Xen emulation of Hyper-V is complete, this will be a problem. Does Xen
return all the "feature bits" of Hyper-V. I could discriminate on a feature that
Xen does not plan to emulate.
>
> > @@ -77,3 +87,32 @@ const __refconst struct hypervisor_x86
> x86_hyper_ms_hyperv = {
> > .init_platform = ms_hyperv_init_platform,
> > };
> > EXPORT_SYMBOL(x86_hyper_ms_hyperv);
> > +
> > +static int vmbus_irq = -1;
> > +static irq_handler_t vmbus_isr;
> > +
> > +void hv_register_vmbus_handler(int irq, irq_handler_t handler)
> > +{
> > + vmbus_irq = irq;
> > + vmbus_isr = handler;
> > +}
> > +EXPORT_SYMBOL_GPL(hv_register_vmbus_handler);
> > +
> > +void hyperv_vector_handler(struct pt_regs *regs)
> > +{
> > + struct pt_regs *old_regs = set_irq_regs(regs);
> > + struct irq_desc *desc;
> > +
> > + irq_enter();
> > +#ifdef CONFIG_X86
> > + exit_idle();
> > +#endif
>
> This being in a file underneath arch/x86 - why the conditional?
Good point, I will fix that.
>
> Jan
>
>
next prev parent reply other threads:[~2013-01-24 16:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 1:17 [PATCH RESEND 1/1] X86: Handle Hyper-V vmbus interrupts as special hypervisor interrupts K. Y. Srinivasan
2013-01-24 8:48 ` Jan Beulich
2013-01-24 16:07 ` KY Srinivasan [this message]
2013-01-24 16:15 ` Jan Beulich
2013-01-24 18:48 ` KY Srinivasan
2013-01-24 18:59 ` Olaf Hering
2013-01-24 19:03 ` KY Srinivasan
2013-01-25 7:32 ` Jan Beulich
2013-01-24 19:04 ` H. Peter Anvin
2013-01-24 19:23 ` Olaf Hering
2013-01-24 19:30 ` H. Peter Anvin
2013-01-25 7:30 ` Jan Beulich
2013-01-25 7:35 ` Jan Beulich
2013-01-25 13:58 ` Olaf Hering
2013-01-24 19:10 ` H. Peter Anvin
2013-01-25 7:31 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2013-01-24 1:56 K. Y. Srinivasan
2013-01-24 9:28 ` Borislav Petkov
2013-01-24 12:11 ` H. Peter Anvin
2013-01-24 17:35 ` Borislav Petkov
2013-01-24 17:36 ` H. Peter Anvin
2013-01-24 17:42 ` KY Srinivasan
2013-01-18 1:55 K. Y. 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=27092660926e4d3f80394697cc0dc858@SN2PR03MB061.namprd03.prod.outlook.com \
--to=kys@microsoft.com \
--cc=JBeulich@suse.com \
--cc=apw@canonical.com \
--cc=bp@alien8.de \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).