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] mmio_decode()

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] mmio_decode()
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Tue, 21 Nov 2006 13:42:45 +0100
Delivery-date: Tue, 21 Nov 2006 04:41:16 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Could anyone enlighten me why this function decodes arbitrary opcodes?
I.e. 0x20...0x23 are all getting decoded, but only 0x00 (and not
0x01...0x03) and only 0x2B (and not 0x2A). I guess this is based on
observed instructions used for mmio, but - this doesn't make sense! That
way, we'll never get to a point where arbitrary OSes (or other
environments) can get emulated.

(To make things odd, I'm complaining about this while the absence of
a decode for 0x00 actually helped pointing out another problem that
I'm in the process of trying to address: Newer isolinux runs partly in
non-flat protected mode, which apparently isn't generally being
considered a supported environment).

Jan

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

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