From: Vince Weaver <vince@csl.cornell.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu as a System Simulator
Date: Wed, 7 Jan 2009 17:37:38 -0500 (EST) [thread overview]
Message-ID: <20090107172617.E43342@stanley.csl.cornell.edu> (raw)
In-Reply-To: <4963B669.2040602@umich.edu>
On Tue, 6 Jan 2009, Andrea Pellegrini wrote:
> I saw that many cycle accurate simulators are based on Qemu and I was
> wondering if anyone has experience and thinks that is possible to modify Qemu
> to support multiple interconnect (such as bus, mesh, NoC).
It's true that some simulation methodologies use Qemu for functional
(correctness) simulation. This is only a small part of a fully functional
"cycle-accurate" simulator. See the
FPGA-Accelerated Simulation Technologies (FAST) work by
Derek Chiou's group:
http://users.ece.utexas.edu/~derek/FAST.html
(I doubt you'll ever see any of their Qemu-related code released)
You can also use Qemu to generate traces for use in simulation.
In some cases, especially on RISC architectures like MIPS, you can
estimate CPI and similar metrics and get results using Qemu
that are similar to those generated by "cycle-accurate" simulators
like SESC. See my paper here for more info on that:
http://www.csl.cornell.edu/~vince/papers/wddd08/index.html
What you describe though would involve adding a lot of extra code to Qemu.
Qemu is set up for fast emulation of binaries, not for architectural
research. There isn't any built in cache or cache-coherence simulation,
let alone any sort of idea of inter-chip interconnects.
So to answer your question, I do think it is possible to use Qemu in the
way you describe. Unfortunately I don't think it's practical or likely to
happen any time soon.
Vince
prev parent reply other threads:[~2009-01-07 22:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 19:52 [Qemu-devel] Qemu as a System Simulator Andrea Pellegrini
2009-01-07 10:22 ` Laurent Desnogues
2009-01-07 22:37 ` Vince Weaver [this message]
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=20090107172617.E43342@stanley.csl.cornell.edu \
--to=vince@csl.cornell.edu \
--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).