From: "John R. Hogerhuis" <jhoger@pobox.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] About qemu emulation speed (a question) and supported OS
Date: Wed, 14 Sep 2005 10:18:24 -0700 [thread overview]
Message-ID: <1126718304.24190.126.camel@aragorn> (raw)
In-Reply-To: <20050914133733.GA6052@jbrown.mylinuxbox.org>
On Wed, 2005-09-14 at 09:37 -0400, Jim C. Brown wrote:
> VMware handles kernel code. You are right that x86 code can't be 100% virtualized
> (even at the userland level) but VMware uses a lot of nasty disgusting tricks
> in order to work around them. (For example, playing with shadow pagetables
> so that a page of modified code is run but if the code tries to inspect itself
> it sees another (unexecuted) page that contains the original code.)
>
Why disgusting?
Seems like a smart implementation given the options at hand.
Perhaps you meant disgusting because the Intel architecture forces a
virtualizer to handle a bunch of corner cases like this.
-- John.
next prev parent reply other threads:[~2005-09-14 17:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 12:36 [Qemu-devel] About qemu emulation speed (a question) and supported OS Alexandre Leclerc
2005-09-13 13:08 ` Adrian Smarzewski
2005-09-13 18:02 ` Alexandre Leclerc
2005-09-13 13:38 ` Jim C. Brown
2005-09-13 14:58 ` Anthony Liguori
2005-09-13 21:48 ` Jim C. Brown
2005-09-14 0:18 ` Mark Williamson
2005-09-14 2:48 ` Anthony Liguori
2005-09-14 3:48 ` Mark Williamson
2005-09-14 4:27 ` Anthony Liguori
2005-09-14 4:58 ` Mike Swanson
2005-09-14 13:39 ` Jim C. Brown
2005-09-14 18:46 ` Anthony Liguori
2005-09-14 22:42 ` Jim C. Brown
2005-09-14 13:37 ` Jim C. Brown
2005-09-14 15:47 ` Henrik Nordstrom
2005-09-14 17:53 ` Mark Williamson
2005-09-14 17:18 ` John R. Hogerhuis [this message]
2005-09-14 22:34 ` Jim C. Brown
2005-09-14 17:46 ` Mark Williamson
2005-09-15 21:26 ` Karl Magdsick
2005-09-15 23:24 ` Mark Williamson
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=1126718304.24190.126.camel@aragorn \
--to=jhoger@pobox.com \
--cc=qemu-devel@nongnu.org \
/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.