From: Laurent Desnogues <laurent.desnogues@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Monitor Memory Accesses
Date: Wed, 18 Feb 2009 14:00:07 +0100 [thread overview]
Message-ID: <761ea48b0902180500wbe676d4x3895d37df10e495b@mail.gmail.com> (raw)
In-Reply-To: <499C03A9.6040003@gmail.com>
On Wed, Feb 18, 2009 at 1:48 PM, Andrea Pellegrini
<andrea.pellegrini@gmail.com> wrote:
> I want to track all the memory accesses performed in a program execution.
> Right now I'm working on an amd64 machine with target x86_64 but eventually
> I would like to do the same for other architectures (at least ARM and PPC).
> With few changes I was able to print out the address of the instructions
> that the processor executes (well at least the first address of the basic
> block)
I guess you're doing that by calling a helper. If you don't, that
won't work :-)
> and now I was looking for a way to record all memory loads and
> stores. I believe I have to change some code in the file translate.c and I
> was wondering if anybody can give me a quick help about which part of code I
> should change. It would be great if I could call a function right before
> every time a load or store is executed.
You should look for parts of translate.c that generate target loads
and stores; basically look for calls to tcg_gen_qemu_ld* and
tcg_gen_qemu_st*.
Laurent
next prev parent reply other threads:[~2009-02-18 13:00 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 [this message]
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
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=761ea48b0902180500wbe676d4x3895d37df10e495b@mail.gmail.com \
--to=laurent.desnogues@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).