From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] About qemu emulation speed (a question) and supported OS
Date: Wed, 14 Sep 2005 13:46:58 -0500 [thread overview]
Message-ID: <43287022.3090106@us.ibm.com> (raw)
In-Reply-To: <20050914133921.GB6052@jbrown.mylinuxbox.org>
Jim C. Brown wrote:
>On Tue, Sep 13, 2005 at 11:27:39PM -0500, Anthony Liguori wrote:
>
>
>>I reckon kqemu has this same problem... Technically, even in ring 3, if
>>you run natively, you violate the Popek/Goldberg requirements because of
>>cpuid. It's just not possible to trap it but it shouldn't matter for
>>most software.
>>
>>
>>
>
>It is possible to trap it, in a sense. You just read ahead and replace the
>cpuid instruction with something else.
>
>
You can't readahead beyond a basic block. Taking a trap for each basic
block and translating the block is what QEMU does.
Regards,
Anthony Liguori
>Ugly, but doable.
>
>
>
next prev parent reply other threads:[~2005-09-14 19:03 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 [this message]
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
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=43287022.3090106@us.ibm.com \
--to=aliguori@us.ibm.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.