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] [PATCH] This patch fixes several issues related to vmxas

To: "Li, Xin B" <xin.b.li@xxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] This patch fixes several issues related to vmxassist
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 31 Mar 2006 13:40:47 +0100
Cc: Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 31 Mar 2006 12:41:50 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <59D45D057E9702469E5775CBB56411F10222B1EA@pdsmsx406>
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: <59D45D057E9702469E5775CBB56411F10222B1EA@pdsmsx406>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 31 Mar 2006, at 12:06, Li, Xin B wrote:

I don't know the heritage of that code. I expect someone
decided it was
good enough to be getting on with but maybe now it is time to revisit
and see if we can implement a watertight version which correctly uses
hidden segment descriptor state which is readily available
when running
on VMX.

My patch just enhanced the current implementation, and actually it
breaks windows, but I have a updated version in hand, and tests show
that all the combinations is OK till now.

In my mind, the correct way is to identify whether a cpu is in big real
mode, but seems this is a little bit hard to do.

Well, it's impossible to know for certain without looking at hidden descriptor state isn't it. Big real mode is only possible because the hidden state can be out of sync with the current execution mode.

If that state can be made available to the address() function then it's implementation, and confidence in its correctness, becomes trivial. Do we have that state available directly in the guest at that point? Or would we need to grab the state from Xen?

 -- Keir


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