qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Diwaker Gupta" <diwaker.lists@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Tracing guest memory accesses
Date: Sat, 16 Dec 2006 19:42:46 -0800	[thread overview]
Message-ID: <891be9410612161942t28116f7w12123ebca0ca6278@mail.gmail.com> (raw)

Hi list,

I've searched the archives and the forums, but couldn't get a specific
solution (I think my search terms might have been too general).
Anyways, I think what I'm trying to do should be relatively easy and
hopefully experts here will be able to quickly point me in the right
direction :)

So I'm just trying to trace all the memory accesses (virtual
addresses) by the guest. I need to trace both reads and writes. If I
can get the exact address, thats great. Otherwise I'm happy with
simply logging the relevant page.

I've uncommented DEBUG_IOMMU in hw/iommu.c and I've added some debug
statements to the io_read and io_write calls in softmmu_template.h. At
this point I have two questions:

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.

o are these changes complete? As in, are there other entry/exit points
in the code for memory accesses that I'm missing.

Thanks,
Diwaker
-- 
Web/Blog/Gallery: http://floatingsun.net/blog

             reply	other threads:[~2006-12-17  3:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-17  3:42 Diwaker Gupta [this message]
2006-12-17  3:53 ` [Qemu-devel] Tracing guest memory accesses Daniel Jacobowitz
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=891be9410612161942t28116f7w12123ebca0ca6278@mail.gmail.com \
    --to=diwaker.lists@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).