From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ARM CPU Speed simulated by Qemu?
Date: Tue, 12 Sep 2006 13:43:35 +0100 [thread overview]
Message-ID: <200609121343.38015.paul@codesourcery.com> (raw)
In-Reply-To: <20060912072037.96809.qmail@web38105.mail.mud.yahoo.com>
On Tuesday 12 September 2006 08:20, Tieu Ma Dau wrote:
> Hi all,
> I found that Qemu ARM system simulates ARM926EJ-S and
> ARM1026EJ-S processor. And I found on ARM website that
> the speed of these CPUs vary from 266 to 540 MHz.
> Could you tell me the exact speed of the ARM926EJ-S
> and ARM1026EJ-S processor simulated by Qemu? It's very
> important for me to finish my report.
Qemu is not cycle accurate. There is no particularly meaningful way to
translate between qemu performance and how fast something will run on real
hardware.
Modern CPUs are complicated, with many factors effecting execution speed
(pipeline interlocks, multiple levels of cache). A cycle accurate simulator
will generally be orders of magnitude slower than qemu.
Paul
next prev parent reply other threads:[~2006-09-12 12:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 19:26 [Qemu-devel] Re: qemu-system-sparc video problem on 16 bitdisplays Blue Swirl
2006-09-12 0:17 ` Stuart Brady
2006-09-12 7:20 ` [Qemu-devel] ARM CPU Speed simulated by Qemu? Tieu Ma Dau
2006-09-12 11:03 ` nyos
2006-09-12 12:43 ` Paul Brook [this message]
2006-09-12 13:19 ` Markus Schiltknecht
2006-09-12 13:39 ` Paul Brook
2006-09-12 14:21 ` Markus Schiltknecht
2006-09-12 14:34 ` Paul Brook
-- strict thread matches above, loose matches on Subject: below --
2006-09-12 14:44 Laurent DESNOGUES
2006-09-12 14:58 ` Markus Schiltknecht
2006-09-12 17:42 ` K. Richard Pixley
2006-09-12 15:08 Laurent DESNOGUES
2006-09-12 15:19 ` Markus Schiltknecht
2006-09-12 15:26 Laurent DESNOGUES
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=200609121343.38015.paul@codesourcery.com \
--to=paul@codesourcery.com \
--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).