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

RE: [Xen-devel] EFER in HVM guests


  • To: "Jan Beulich" <jbeulich@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
  • Date: Wed, 29 Nov 2006 14:11:58 +0100
  • Delivery-date: Wed, 29 Nov 2006 05:15:31 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AccTtyFTcsh6aLjCSJ62PO4XA9EJ5gAAA7Xw
  • Thread-topic: [Xen-devel] EFER in HVM guests

 

> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Jan Beulich
> Sent: 29 November 2006 13:07
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-devel] EFER in HVM guests
> 
> Is it intentional that
> - under SVM, 32-bit guests can freely set EFER.LME

Ehm, I guess you mean "on 32-bit hypervisor", as it's impossible to
distinguish a 32-bit and 64-bit guest until the guest is setting LME...
;-). 

The correct reaction for a 32-bit hypervisor is to react like a
"non-64-bit capable processor", which means that EFER has the LME as a
mbz-bit. GP-fault if it's written as a one. We do prevent the long-mode
from being advertised by CPUID when HV is in 32-bit mode, so if the
guest is well-behaved, it shouldn't try to set this bit. 

--
Mats

> - under VMX, 32-bit guests can't access EFER at all?
> 
> Thanks, Jan
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 
> 
> 



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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