From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <jbeulich@novell.com>
Subject: mmio_decode()
Date: Tue, 21 Nov 2006 13:42:45 +0100
Message-ID: <45630255.76E4.0078.0@novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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