From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-fast - a better howto?
Date: Tue, 02 Mar 2004 14:41:18 +0100 [thread overview]
Message-ID: <40448EFE.4000104@bellard.org> (raw)
> What about a better howto about qemu-fast (how to set up, etc.)
I will update the documentation for the next release. My idea is to
split it between user documentation and technical documentation.
I will also make a fix for the compilation of qemu-fast for the LDT problem.
The current state of qemu-fast in CVS is that it can only launch patched
OSes, but at near native speeds (no precise benchmarks yet).
The specific "roadmap" for qemu-fast is:
- native floating point support (qemu-fast still uses full emulation for
floating point, which is slow).
- faster self modifying code support (qemu-fast is slower than qemu on
16 bit code which heavily uses self modifying code).
- faster memory mapped device access (qemu-fast is slower than qemu for
VGA emulation).
- huge memory support (qemu-fast can simulate up to 256 MB of RAM, but
this limit will be increased to 4 GB, and then 64 GB).
Fabrice.
next reply other threads:[~2004-03-02 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 13:41 Fabrice Bellard [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-01 17:30 [Qemu-devel] qemu-fast - a better howto? Gabriel Guzmics
2004-03-02 0:17 ` Gabriel Ebner
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=40448EFE.4000104@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 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.