From: Struan Bartlett <struan@praguespringpeople.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qvm86, kqemu and video speed
Date: Mon, 11 Apr 2005 16:07:44 +0200 [thread overview]
Message-ID: <425A84B0.60200@praguespringpeople.org> (raw)
Hi,
I've run some Windows 2000 performance tests on Qemu using a program
called PassMark PerformanceTest. You can find some results here -
http://www.praguespringpeople.org/Struan/Software/QEMU/Performance/2005-03-29/
- I'll put more there when I make them.
The results seem to me to suggest that emulated performance is weakest
on video operations - which doesn't surprise me if it is necessary for
every pixel change to be emulated - and while this won't be an issue for
some Qemu users it will I expect be a major issue for others.
I understand qvm86 and kqemu provide some virtualisation of the host
machine, including allowing the guest some direct memory access. Is it
conceivable for these modules to be extended to allow the guest machine
to directly write to host video memory, or else to a host memory buffer
that is copied into the Qemu window?
Struan
next reply other threads:[~2005-04-11 13:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-11 14:07 Struan Bartlett [this message]
2005-04-11 15:01 ` [Qemu-devel] qvm86, kqemu and video speed James Mastros
2005-04-11 15:17 ` Paul Brook
2005-04-11 15:35 ` Struan Bartlett
2005-04-11 21:51 ` Struan Bartlett
2005-04-15 8:54 ` Struan Bartlett
2005-04-12 3:13 ` Darryl Dixon
2005-04-11 21:53 ` Struan Bartlett
2005-04-12 16:38 ` Alex Beregszaszi
2005-04-12 19:30 ` Fabrice Bellard
2005-04-13 3:57 ` use.reply-to.address
2005-04-13 8:06 ` Struan Bartlett
2005-04-13 18:12 ` Hetz Ben Hamo
2005-04-13 19:24 ` Leonardo E. Reiter
2005-04-13 20:09 ` Leonardo E. Reiter
2005-04-14 9:42 ` Thomas Steffen
2005-04-18 7:32 ` Oliver Gerlich
2005-04-19 6:15 ` emuls
2005-04-13 21:12 ` Jim C. Brown
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=425A84B0.60200@praguespringpeople.org \
--to=struan@praguespringpeople.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).