From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] USE_CODE_COPY
Date: Tue, 18 Jul 2006 23:06:53 +0200 [thread overview]
Message-ID: <44BD4D6D.2050407@bellard.org> (raw)
In-Reply-To: <44BCD59B.7040404@null.gr>
Hi,
USE_CODE_COPY is only used for user level emulation. My current plan is
to remove this code ASAP because it adds too much complexity to QEMU and
has little use.
IMHO it is more useful to concentrate on making the x86 target more
accurate (e.g. FPU support in SOFT_FLOAT mode, full segment checks, SMI
mode) while being totally independent of the x86 host.
The case where performance is needed can be handled more efficiently by
using kqemu or qvm86.
Regards,
Fabrice.
Petros Efstathopoulos wrote:
> Hi all.
>
> I was looking at the qemu dynamic rewriting code for system emulation
> (and NOT running user level processes). Is direct copying
> (USE_CODE_COPY) ever used? It looks to me that it's not, since the
> softmmu is always used...
>
> I am mostly interested in the X86_64 target.
>
> thanks,
> -Petros.
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
>
prev parent reply other threads:[~2006-07-18 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 12:35 [Qemu-devel] USE_CODE_COPY Petros Efstathopoulos
2006-07-18 21:06 ` Fabrice Bellard [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=44BD4D6D.2050407@bellard.org \
--to=fabrice@bellard.org \
--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).