From: Piotras <piotras@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu code copy
Date: Sun, 21 Nov 2004 12:01:34 +0100 [thread overview]
Message-ID: <da6318370411210301742b3e30@mail.gmail.com> (raw)
In-Reply-To: <419EE215.5000701@chesstrain.com>
Hi!
Code copy works by executing original code blocks (no translation
is performed) when possible. If the block contains memory access
instruction, it can be executed in code-copy mode only when virtual
memory of emulated CPU is visible as qemu process virtual memory.
This is what qemu-fast does with mmap.
I think that in practice nearly all code blocks contain memory access
instructions. If so, it's not worth to enable code-copy for qemu-soft.
Probably it's possible to build simple code translator that would
translate only memory access instructions and execute most of
the other instructions natively.
Regards,
Piotrek
On Fri, 19 Nov 2004 22:20:05 -0800, Shivkumar Shivaji
<shivdev@chesstrain.com> wrote:
> Is there anything preventing qemu regular (not qemu-fast) from using
> code-copy? Currently, code copy only works on hard mmu. Is there a way
> to enable it on the regular qemu?
prev parent reply other threads:[~2004-11-21 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 18:13 [Qemu-devel] VNC patch Piotr R.
2004-11-20 6:20 ` [Qemu-devel] Qemu code copy Shivkumar Shivaji
2004-11-21 11:01 ` Piotras [this message]
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=da6318370411210301742b3e30@mail.gmail.com \
--to=piotras@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).