From: Keir Fraser <keir@xensource.com>
To: Jan Beulich <jbeulich@novell.com>, xen-devel@lists.xensource.com
Subject: Re: mmio_decode()
Date: Tue, 21 Nov 2006 13:44:58 +0000 [thread overview]
Message-ID: <C188B35A.4D25%keir@xensource.com> (raw)
In-Reply-To: <45630255.76E4.0078.0@novell.com>
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
prev parent reply other threads:[~2006-11-21 13:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 12:42 mmio_decode() Jan Beulich
2006-11-21 13:44 ` Keir Fraser [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C188B35A.4D25%keir@xensource.com \
--to=keir@xensource.com \
--cc=jbeulich@novell.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.