From: Fabrice Bellard <fabrice.bellard@free.fr>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Code Copy / New Linux boot code
Date: Mon, 16 Feb 2004 01:07:30 +0100 [thread overview]
Message-ID: <403009C2.8000505@free.fr> (raw)
Just to give more information about the next commits:
1) I finally added a hand coded x86 to x86 translator. It means that
qemu-fast has now close to native performances on x86. Who spoke about
PC virtualization ? :-)
The x86 to x86 translator is limited to flat 32 bit mode and it does not
support floating point (yet !). If the translator cannot handle a given
instruction, then the "portable" translator is used as a fallback.
2) qemu-fast is being enhanced to run unpatched OSes and to support VESA
VBE graphics.
The limitations of qemu-fast are that if data at addresses >= 0xc0000000
is used, then soft MMU is used in the corresponding translated block.
Moreover, the guest user code has write access to the guest OS code and
also to the host QEMU code. It means that qemu-fast is not safe. I don't
know yet what is the best way to solve this issue.
3) A new and simpler Linux kernel loader has been added (for the
'-kernel' command line option). Now the PC BIOS and the VGA BIOS are run
before running the kernel, which gives exactly the same behavior as if
the kernel was booted normally.
Fabrice.
next reply other threads:[~2004-02-16 0:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 0:07 Fabrice Bellard [this message]
2004-02-16 0:27 ` [Qemu-devel] Code Copy / New Linux boot code Grzegorz Kulewski
2004-02-16 0:40 ` Fabrice Bellard
2004-02-16 0:52 ` Jamie Burns
2004-02-16 3:43 ` Ed Suominen
2004-02-16 7:27 ` Michael Torrie
2004-02-16 12:33 ` Lionel Ulmer
2004-02-16 18:02 ` Michael Torrie
2004-02-16 18:10 ` Rutger Nijlunsing
2004-02-16 20:25 ` Gabriel Ebner
2004-02-16 20:26 ` Michael Torrie
2004-02-29 21:24 ` Derrik Pates
2004-03-03 14:58 ` Artur Skawina
2004-03-05 8:23 ` John R. Hogerhuis
2004-03-08 23:23 ` Michael L Torrie
2004-02-16 20:17 ` Lionel Ulmer
2004-02-16 20:33 ` Michael Torrie
2004-02-17 0:10 ` Jamie Burns
2004-02-17 0:23 ` Michael Torrie
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=403009C2.8000505@free.fr \
--to=fabrice.bellard@free.fr \
--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).