From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir@xensource.com>
Subject: Re: mmio_decode()
Date: Tue, 21 Nov 2006 13:44:58 +0000
Message-ID: <C188B35A.4D25%keir@xensource.com>
References: <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>
In-Reply-To: <45630255.76E4.0078.0@novell.com>
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: Jan Beulich <jbeulich@novell.com>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org




On 21/11/06 12:42, "Jan Beulich" <jbeulich@novell.com> wrote:

> 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.

Opcodes get faulted in as needed. Pretty stupid I agree.

 -- Keir