From: "J. Mayer" <l_indien@magic.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Power PC speed?
Date: Wed, 19 May 2004 11:11:48 +0200 [thread overview]
Message-ID: <1084957907.8244.6765.camel@rapid> (raw)
In-Reply-To: <000a01c43d30$5509d9d0$0202a8c0@Shaggy>
On Wed, 2004-05-19 at 01:32, Jamie Burns wrote:
> Hi,
>
> With all the commotion surrounding PearPC and its ability to install
> Mac OS X, I was wondering what the rough speed of QMEU's PowerPC
> system emulation? The PearPC JIT system runs at about 1/40th the speed
> of its host. Anybody have a rough idea how the current QEMU compares?
I made differents tests:
Linux kernel compilation and nbench.
I promise to put detailed benches on my page soon :-)
My conclusion is:
the code I'm working on is equivalent to a 200 Mhz PPC on my amd64 3000+
(2Ghz).
Nbench gives 1/15 ratio, which seems coherent.
The CVS code is about two or three times slower because I do a lot of
context synchronisations that a real CPU won't do and this makes context
switches very slow: this really slows down tests like "make olconfig" on
a Linux kernel: makes does a lot of forks.
--
J. Mayer <l_indien@magic.fr>
Never organized
next prev parent reply other threads:[~2004-05-19 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 23:32 [Qemu-devel] Power PC speed? Jamie Burns
2004-05-19 9:11 ` J. Mayer [this message]
2004-05-19 10:46 ` Jean-Michel POURE
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=1084957907.8244.6765.camel@rapid \
--to=l_indien@magic.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).