From: Luis Useche <luis@cs.fiu.edu>
To: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Memory Traces for System Simulation
Date: Thu, 18 Jun 2009 15:48:20 -0400 [thread overview]
Message-ID: <20090618194820.GA19814@meg.cs.fiu.edu> (raw)
In-Reply-To: <20090618152005.GC16663@edde.se.axis.com>
On Thu, Jun 18, 2009 at 05:20:05PM +0200, Edgar E. Iglesias wrote:
> On Wed, Jun 17, 2009 at 05:50:18PM -0400, Luis Useche wrote:
> > Hi Guys,
>
> Hello Luis,
Thanks for the response.
> > At the moment, I am instrumenting several functions in exec.c as my trace
> > points:
> > ldl_phys
> > ldq_phys
> > ldup_phys
> > lduw_phys
> > stl_phys_notdirty
> > stq_phys_notdirty
> > stl_phys
> > stb_phys
> > stw_phys
> > stq_phys
>
> Depending on what you want to do and on your cache arch you might need
> to log both virtual and physical addresses. I don't know what the best
> place to hook in would be though.
If I can find the physical addresses that would be really great. And if I
can find both physical and virtual it would be even better. In any case, I
need to know what section of the code is the most likely to have this
memory operations to trace them.
> > I would really appreciate any suggestion you have in order to solve my
> > problem. If you have any insights in the solutions I explained above I
> > would be very thankful.
> >
> > Given that many people seems to be having the same problem than I, it
> > would be nice to have an actual framework that add this functionality to
> > qemu. I can offer myself to do that as long as I have enough help.
> >
> > As a parallel question: Does qemu simulate CPU cache? i.e. There is always
>
> Nope.
>
> > memory access even when this would not happen in a real system due to CPU
> > cache?
>
> Yes correct.
>
> I've got a pretty nasty hack that online emulates controller and tag
> memories. I find it useful for profiling and for some debugging. The data
> memories are not emulated so accesses are never absorbed. I don't think
> it's very useful for scientific purposes..
>
> Anyway, it kind of works for CRIS and MicroBlaze. Feel free to look around
> on the cris git at your own risk :)
> git://repo.or.cz/qemu/cris-port.git
This can probably helps. Can you give me more information of what this
does.
Best,
--
Luis Useche <luis@cs.fiu.edu>
Ph.D. Student
Florida International University
next prev parent reply other threads:[~2009-06-18 19:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 21:50 [Qemu-devel] Memory Traces for System Simulation Luis Useche
2009-06-18 14:28 ` Luis Useche
2009-06-18 15:20 ` Edgar E. Iglesias
2009-06-18 19:48 ` Luis Useche [this message]
2009-06-18 21:18 ` Edgar E. Iglesias
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=20090618194820.GA19814@meg.cs.fiu.edu \
--to=luis@cs.fiu.edu \
--cc=edgar.iglesias@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).