linux-kernel - RE: [PATCH RESEND 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: <462e0bc4257744428139d5dbc91192be@SN2PR03MB061.namprd03.prod.outlook.com>
Date:	Thu, 24 Jan 2013 19:03:42 +0000
From:	KY Srinivasan <kys@...rosoft.com>
To:	Olaf Hering <olaf@...fle.de>
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



> -----Original Message-----
> From: Olaf Hering [mailto:olaf@...fle.de]
> Sent: Thursday, January 24, 2013 2:00 PM
> To: KY Srinivasan
> Cc: Jan Beulich; bp@...en8.de; apw@...onical.com; x86@...nel.org;
> tglx@...utronix.de; devel@...uxdriverproject.org; gregkh@...uxfoundation.org;
> jasowang@...hat.com; linux-kernel@...r.kernel.org; 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.

I was under the impression that only Dom0 Xen would emulate Hyper-V.


K. Y
> 
> Olaf
>