From: Derek Fawcus <dfawcus@cisco.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] full speed ?
Date: Sat, 5 Jun 2004 19:22:45 +0100 [thread overview]
Message-ID: <20040605192244.B1510@edinburgh.cisco.com> (raw)
In-Reply-To: <40C1FFA1.5000804@dad-answers.com>; from hetz@dad-answers.com on Sat, Jun 05, 2004 at 08:15:13PM +0300
On Sat, Jun 05, 2004 at 08:15:13PM +0300, Hetz Ben Hamo wrote:
> There are other plans to make it much faster (X86 on X86) but it
> cannot be discussed it at the moment..
Cannot be discussed? Well the obvious approach is to split the program
such that user mode code runs in a seperate process, then arrange for
that process to be controlled by the main process as a debugee.
Then the main process has complete control over the child, and can mess
with it (including memory mappings, cataching signals and syscalls) to
it's heart's content. This would allow user space to run at full speed,
while still having the system space running in the emulated dynamic
translation system.
It'd take some work to do this, and get the synchronisation working
correctly, but as I said it's the 'obvious' approach. It also has
the advantage that it would work well on x86-64.
DF
prev parent reply other threads:[~2004-06-05 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-05 17:32 [Qemu-devel] full speed ? vaise
2004-06-05 17:15 ` Hetz Ben Hamo
2004-06-05 18:22 ` Derek Fawcus [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=20040605192244.B1510@edinburgh.cisco.com \
--to=dfawcus@cisco.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).