From: Daniel Jacobowitz <drow@false.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Tracing guest memory accesses
Date: Sat, 16 Dec 2006 22:53:07 -0500 [thread overview]
Message-ID: <20061217035307.GA32712@nevyn.them.org> (raw)
In-Reply-To: <891be9410612161942t28116f7w12123ebca0ca6278@mail.gmail.com>
On Sat, Dec 16, 2006 at 07:42:46PM -0800, Diwaker Gupta wrote:
> o do these changes seem correct? As in, do they actually track the
> read/write memory accesses done by the guest? I was concerned because
> when I start a guest, I see a whole lot of writes and not as many
> reads, which seems a little counter intuitive.
No. Those are I/O device accesses, not memory accesses. Look at the
softmmu code instead.
It may be easiest to add some new instrumentation in the translation
code for whatever target you're interested in.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-12-17 3:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-17 3:42 [Qemu-devel] Tracing guest memory accesses Diwaker Gupta
2006-12-17 3:53 ` Daniel Jacobowitz [this message]
2006-12-17 7:19 ` Diwaker Gupta
2006-12-17 11:52 ` maestro
2006-12-18 8:56 ` Diwaker Gupta
2006-12-18 19:49 ` maestro
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=20061217035307.GA32712@nevyn.them.org \
--to=drow@false.org \
--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).