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

[Xen-devel] x86 emulator and new isa additions

To: "Keir Fraser" <keir@xxxxxxx>
Subject: [Xen-devel] x86 emulator and new isa additions
From: "Jan Beulich" <JBeulich@xxxxxxxx>
Date: Tue, 15 Nov 2011 13:03:32 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 15 Nov 2011 05:05:51 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Keir,

so far the convention seems to be to assume that guest attempts to
execute instructions not supported by the underlying CPU would never
make it into the emulator. Is that really correct (in particular in the
context of real mode emulation, where it's not just single instructions
that get emulated)?

>From earlier work on the emulation code I seem to recall that it's mainly
the testing code that didn't like use of cpu_has_xyz in conditionals. I
would suppose that simply adding respective feature detection (and
boolean variables) to the testing code should get us around this
problem. Or would you see any better alternative?

Jan


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

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