[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] x86/hvm: Conditionally leave CPUID Faulting active in HVM context


  • To: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Tue, 24 Jan 2017 07:58:56 +0000
  • Accept-language: en-US
  • Cc: "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>
  • Delivery-date: Tue, 24 Jan 2017 07:59:23 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: AQHSb+otyN2r8/QxxUaDMaOI0Apf4qFFp5QAgAGnuRA=
  • Thread-topic: [PATCH] x86/hvm: Conditionally leave CPUID Faulting active in HVM context

> From: Andrew Cooper [mailto:andrew.cooper3@xxxxxxxxxx]
> Sent: Monday, January 23, 2017 10:41 PM
> 
> On 16/01/17 11:17, Andrew Cooper wrote:
> > If the hardware supports faulting, and the guest has chosen to use it, leave
> > faulting active in HVM context.
> >
> > It is more efficient to have hardware convert CPUID to a #GP fault (which we
> > don't intercept), than to take a VMExit and have Xen re-inject a #GP fault.
> >
> > Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
> > ---
> > CC: Jan Beulich <JBeulich@xxxxxxxx>
> > CC: Jun Nakajima <jun.nakajima@xxxxxxxxx>
> > CC: Kevin Tian <kevin.tian@xxxxxxxxx>
> 
> Ping VT-x ?
> 

sorry overlooked this one:

Reviewed-by: Kevin Tian <kevin.tian@xxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.