From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Windows 98 - hardware
Date: Wed, 05 May 2004 00:38:42 +0200 [thread overview]
Message-ID: <40981B72.8030408@bellard.org> (raw)
In-Reply-To: <1083681962.1484.2.camel@debian>
Lean Fuglsang wrote:
>>This is no longer right. qemu-fast will be able someday to run all OSes,
>>but the price to pay will be less security (the emulated user space code
>>will be able to write to the QEMU cpu code).
>
> Okay, as long as I can put qemu into a seperate user that is fine.
> And if Windows crashes, a virtual reboot is needed anyway.
> How much performance gain is the in using qemu-fast? Is it something I
> should look forward, or is it neglictible?
The performance gain will be important, especially for purely
computational user tasks (close to native performances). The OS kernel
itself will run at about the same speed as the 'standard' qemu.
To do better, a host kernel module will be needed, but I don't have the
courage to do that yet.
> (I don't dare to ask for the timeframe ;)
Yes, it is better not to ask :-)
Fabrice.
next prev parent reply other threads:[~2004-05-04 23:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-04 2:47 [Qemu-devel] Windows 98 - hardware Jim C. Brown
2004-05-04 3:19 ` Fabrice Bellard
2004-05-04 14:46 ` Lean Fuglsang
2004-05-04 15:44 ` [Qemu-devel] Interesting progress with Win2k Jason Gress
2004-05-04 16:30 ` [Qemu-devel] w2k install problem & interesting progress Sebastien Bechet
2004-05-12 21:40 ` [Qemu-devel] QEMU OS Support Table Fabrice Bellard
2004-05-12 21:57 ` Grzegorz Kulewski
2004-05-04 22:38 ` Fabrice Bellard [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-03 19:11 [Qemu-devel] Windows 98 - hardware Lean Fuglsang
2004-05-03 19:51 ` Jim C. Brown
2004-05-03 21:22 ` Lean Fuglsang
2004-05-03 21:31 ` Hetz Ben Hamo
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=40981B72.8030408@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).