qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Markus Schiltknecht <markus@bluegap.ch>
To: laurent.desnogues@wanadoo.fr, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ARM CPU Speed simulated by Qemu?
Date: Tue, 12 Sep 2006 16:58:36 +0200	[thread overview]
Message-ID: <4506CB1C.2030109@bluegap.ch> (raw)
In-Reply-To: <21288277.1158072277598.JavaMail.www@wwinf1515>

Hi,

Laurent DESNOGUES wrote:
> The most complex thing to accurately simulate a modern
> CPU (including ARMs) is the data cache and by far. 

Hm... you have to elaborate on that one. Aren't those caches like other 
caches, too? With well known algorithms like LRU?

> In
> comparison, getting accurate core pipeline simulation
> is *very* easy.

Simulating branch prediction seems more complex to me (probably because 
I'm thinking x86, not ARM).

What to others think about the network and hard disk simulation I've
mention in my previous post?

Regards

Markus

  reply	other threads:[~2006-09-12 14:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-12 14:44 [Qemu-devel] ARM CPU Speed simulated by Qemu? Laurent DESNOGUES
2006-09-12 14:58 ` Markus Schiltknecht [this message]
2006-09-12 17:42 ` K. Richard Pixley
2006-09-12 18:40 ` [Qemu-devel] " Antti P Miettinen
  -- strict thread matches above, loose matches on Subject: below --
2006-09-12 15:26 [Qemu-devel] " Laurent DESNOGUES
2006-09-12 15:08 Laurent DESNOGUES
2006-09-12 15:19 ` Markus Schiltknecht
2006-09-12  0:17 [Qemu-devel] Re: qemu-system-sparc video problem on 16 bitdisplays 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
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

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=4506CB1C.2030109@bluegap.ch \
    --to=markus@bluegap.ch \
    --cc=laurent.desnogues@wanadoo.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).