From: Dan Sandberg <dan.sandberg@medsci.uu.se>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] win98 slow with kqemu
Date: Tue, 02 Jan 2007 13:54:50 +0100 [thread overview]
Message-ID: <459A561A.4050704@medsci.uu.se> (raw)
In-Reply-To: <200612301809.30656.mr@ramendik.ru>
I have noticed the same thing.
Could it be that todays processors are simply very bad at running 16-bit
code (that the pipeline has to be reloaded for each instruction or
something similar)?
If this is the case there is probably nothing else to do than avoiding
kqemu with 16-bit OS:s.
On the other hand, if for instance VMware is able to run Windows 98 much
faster (I do not have it so I can't test this) then my guess is that
kqemu is the guilty part and does something wrong with 16-bit code.
Regards
Dan Sandberg
Mikhail Ramendik wrote:
>Hello,
>
>Some time ago I reported win98 slowness with kqemu, see
>http://lists.gnu.org/archive/html/qemu-devel/2006-05/msg00295.html
>
>I have tried again, this time on a Pentium 4 (Prescott) 3 GHz system, with
>Debian sarge and backports.org 2.6.18 kernel; qemu 0.8.2 and kqemu 1.3.0pre9
>are locally compiled, not packaged.
>
>Still I see visible slowness with win98 guest and kqemu; it is slower than
>win98 guest without kqemu. The amnhld.vxd idlesness driver is installed.
>
>The problem is mentioned in forums periodically, i.e. the last reply in
>http://qemu-forum.ipi.fi/viewtopic.php?t=2015 .
>
>I would really like to have this fixed; I am somewhat experienced and will do
>what is needed for testing etc. I would try some CPU "mark" tests for a more
>objective check - but which of them will work without DirectX?
>
>
>
next prev parent reply other threads:[~2007-01-02 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-30 18:09 [Qemu-devel] win98 slow with kqemu Mikhail Ramendik
2007-01-02 12:54 ` Dan Sandberg [this message]
2007-01-06 17:43 ` Mikhail Ramendik
2007-01-08 10:11 ` Dan Sandberg
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=459A561A.4050704@medsci.uu.se \
--to=dan.sandberg@medsci.uu.se \
--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).