From: Leendert van Doorn <leendert@watson.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Mats <Mats.Petersson@amd.com>,
xen-devel <xen-devel@lists.xensource.com>,
Khoa Huynh <khoa@us.ibm.com>
Subject: Re: [PATCH] Calculate correct instruction length for data-fault VM exits on VT-x systems
Date: Sat, 29 Apr 2006 19:24:13 -0400 [thread overview]
Message-ID: <1146353053.2528.36.camel@localhost.localdomain> (raw)
In-Reply-To: <18dbf8579f22244039cabdf6da372735@cl.cam.ac.uk>
On Sat, 2006-04-29 at 11:39 +0100, Keir Fraser wrote:
>
> Xen-emulated devices could have their state fetched on demand -- it
> ought to be rare that qemu-dm ends up emulating an access to such a
> device. Or have qemu call down into Xen to emulate those accesses.
> Having a device model duplicated in both Xen and qemu, and
> synchronising between the two, sounds a bit sketchy.
In the BIOS (realmode) these devices are initialized and the subsequent
32-bit code depends on the proper initialization. For the common I/O
emulation case this should hopefully be rare.
Leendert
next prev parent reply other threads:[~2006-04-29 23:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 9:19 [PATCH] Calculate correct instruction length for data-fault VM exits on VT-x systems Petersson, Mats
2006-04-28 9:24 ` Keir Fraser
2006-04-29 1:20 ` Leendert van Doorn
2006-04-28 20:02 ` Anthony Liguori
2006-04-29 8:00 ` Keir Fraser
2006-04-29 14:54 ` Leendert van Doorn
2006-04-29 10:39 ` Keir Fraser
2006-04-29 23:24 ` Leendert van Doorn [this message]
2006-04-29 18:54 ` Keir Fraser
2006-04-30 1:37 ` Leendert van Doorn
2006-04-29 19:46 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2006-05-02 12:36 Petersson, Mats
2006-04-28 9:02 Petersson, Mats
2006-04-28 9:14 ` Keir Fraser
2006-04-28 1:52 Khoa Huynh
2006-04-28 2:41 ` Anthony Liguori
2006-04-28 6:03 ` Keir Fraser
2006-04-28 18:10 ` Khoa Huynh
2006-04-29 7:21 ` Keir Fraser
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=1146353053.2528.36.camel@localhost.localdomain \
--to=leendert@watson.ibm.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=Mats.Petersson@amd.com \
--cc=khoa@us.ibm.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.