From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leendert van Doorn 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 Message-ID: <1146353053.2528.36.camel@localhost.localdomain> References: <907625E08839C4409CE5768403633E0BA7FC0B@sefsexmb1.amd.com> <1146273618.4268.32.camel@localhost.localdomain> <1146322494.2528.19.camel@localhost.localdomain> <18dbf8579f22244039cabdf6da372735@cl.cam.ac.uk> Reply-To: leendert@watson.ibm.com Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <18dbf8579f22244039cabdf6da372735@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Mats , xen-devel , Khoa Huynh List-Id: xen-devel@lists.xenproject.org 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