WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] VMX check in /xen/arch/x86/domain.c is invalid onx86-64

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] VMX check in /xen/arch/x86/domain.c is invalid onx86-64 (at least AMD)
From: "Jonathan S. Shapiro" <shap@xxxxxxxxxxx>
Date: Thu, 12 May 2005 05:11:31 -0400
Delivery-date: Thu, 12 May 2005 09:05:20 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <7F740D512C7C1046AB53446D3720017303F6518F@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <7F740D512C7C1046AB53446D3720017303F6518F@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 2005-05-11 at 22:28 -0700, Nakajima, Jun wrote:
> Jerone Young wrote:
> > if (!(c->flags & ECF_VMX_GUEST))
> >         if ( ((c->cpu_ctxt.cs & 3) == 0) ||
> >              ((c->cpu_ctxt.ss & 3) == 0) )
> >                 return -EINVAL;
> > 
> > This check in /xen/arch/x86/domain.c (line 394) is invalid for AMD
> > x86-64 as this field 1<<1 is a reserved field in the rflags (name for
> > 64bit eflags) that reads as 1. This can be found in the AMD x86-64
> > Programming manual vol 2 on page 65. Below is the code, I'm not sure
> > how to put an ifdef around since I'm not sure if Intel's EMT64 with
> > VMX cpus have the same rflag reserved (which if this check is correct
> > they do)? This helps break x86-64 building domU domains.
> 
> This c->flags has nothing to do with the machine architecture, but it's
> just a software field for the domain builder to specify the type of the
> domain (i.e. VMX or not, for example). The rflags is in
> execution_context_t.

Then it *definitely* should not be named flags. Perhaps rename to
domFlags?


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

<Prev in Thread] Current Thread [Next in Thread>