From: Andrea Pellegrini <andrea.pellegrini@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Monitor Memory Accesses
Date: Wed, 18 Feb 2009 14:04:14 -0500 [thread overview]
Message-ID: <499C5BAE.40202@gmail.com> (raw)
In-Reply-To: <20090218132622.U28170@stanley.csl.cornell.edu>
I agree.
I only need a basic timing simulation, I can start simply with CPI=1,
issue one instruction per clock, assume a perfect branch predictor and
calling good for right now.
Thanks for the link to the code, I'll take a look at your patch in the
afternoon,
~Andrea
Vince Weaver wrote:
> On Wed, 18 Feb 2009, Andrea Pellegrini wrote:
>> nice to talk to you again. I figured that we are trying to do
>> basically the same thing. Are you able to use the traces from Qemu
>> with Dinero? If so, in case of cache miss, can you stall the
>> execution of Qemu for some cycles?
>
> You can use Qemu to generate traces for Dinero, patches for that were
> previously mentioned in this thread.
>
> Stalling is meaningless though... Qemu is not cycle-accurate.
>
> If you really want cycle accurate values, you're going to have to feed
> the traces from Qemu into a timing simulator. It might be possible to
> create a simple mips timing simulator that hooks into Qemu (see my
> wddd 2008 paper) but that would involve significant hacking that's not
> really related to Qemu development.
>
> Vince
>
>
>
>
>
>
prev parent reply other threads:[~2009-02-18 19:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 12:48 [Qemu-devel] Monitor Memory Accesses Andrea Pellegrini
2009-02-18 13:00 ` Laurent Desnogues
2009-02-18 13:17 ` Andrea Pellegrini
2009-02-18 13:26 ` Laurent Desnogues
2009-02-18 15:40 ` Andrea Pellegrini
2009-02-18 15:52 ` Laurent Desnogues
2009-02-18 16:14 ` Vince Weaver
2009-02-18 16:36 ` Andrea Pellegrini
2009-02-18 18:30 ` Vince Weaver
2009-02-18 19:04 ` Andrea Pellegrini [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=499C5BAE.40202@gmail.com \
--to=andrea.pellegrini@gmail.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).