[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] mmio_decode()


  • To: Jan Beulich <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxxxxxxxx>
  • Date: Tue, 21 Nov 2006 13:44:58 +0000
  • Delivery-date: Tue, 21 Nov 2006 05:45:42 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AccNczvberF5wXlmEduJYgAX8io7RQ==
  • Thread-topic: [Xen-devel] mmio_decode()



On 21/11/06 12:42, "Jan Beulich" <jbeulich@xxxxxxxxxx> 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


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.