RE: [Xen-devel] [PATCH] Calculate correct instruction length for

On Sat, 2006-04-29 at 16:48 +0100, Ian Pratt wrote:

> Having a full emulator available certainly enables lots of cool tricks
> (e.g. the taint tracking example in the paper). You wouldn't want to use
> it for all MMIO operations (they're often singletons), but for handling
> batches is would be good. It's certainly a good way of handling the 16b
> issue on Intel.

Why wouldn't you do it on each mmio operation that is not implemented in
the hypervisor? As soon as you have to do the upcall the cost of going
to qemu-dm, or even a miniguest partition, dwarfs the cost of invoking
the emulator.

        Leendert

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

<Prev in Thread]	Current Thread	[Next in Thread>
RE: [Xen-devel] [PATCH] Calculate correct instruction length fordata-fault VM exits on VT-x systems, Ian Pratt RE: [Xen-devel] [PATCH] Calculate correct instruction length fordata-fault VM exits on VT-x systems, Leendert van Doorn <=

Previous by Date:

RE: [Xen-devel] peth0 received packet on own address, Ian Pratt

Next by Date:

Re: [Xen-devel] [PATCH] Calculate correct instruction length for data-fault VM exits on VT-x systems, Leendert van Doorn

Previous by Thread:

RE: [Xen-devel] [PATCH] Calculate correct instruction length fordata-fault VM exits on VT-x systems, Ian Pratt

Next by Thread:

[Xen-devel] Testing status of fully virtualized guests (Intel VT) on 32bit XEN unstable, Ed Smith

Indexes:

[Date] [Thread] [Top] [All Lists]