[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130124185943.GA19194@aepfle.de>
Date: Thu, 24 Jan 2013 19:59:43 +0100
From: Olaf Hering <olaf@...fle.de>
To: KY Srinivasan <kys@...rosoft.com>
Cc: Jan Beulich <JBeulich@...e.com>, "bp@...en8.de" <bp@...en8.de>,
"apw@...onical.com" <apw@...onical.com>,
"x86@...nel.org" <x86@...nel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"jasowang@...hat.com" <jasowang@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"hpa@...or.com" <hpa@...or.com>
Subject: Re: [PATCH RESEND 1/1] X86: Handle Hyper-V vmbus interrupts as
special hypervisor interrupts
On Thu, Jan 24, KY Srinivasan wrote:
> > Question is - considering you stated that this is supported
> > starting in Win8, doesn't Hyper-V itself announce that
> > capability in some explicit way?
>
> Thanks Jan. Unfortunately I don't think tis interrupt delivery model
> is specified via a "feature" bit (I will check with the Windows guys).
> Perhaps, we can have a Hyper-V specific compilation switch to address
> the Xen emulation issue.
Would that really help if both pvops XEN_PVHVM and HYPERV are enabled in
the config? I assume at this point the access to the DMI data is not yet
possible.
Olaf
--
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/
Powered by blists - more mailing lists