qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Diwaker Gupta" <diwaker.lists@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Tracing guest memory accesses
Date: Sat, 16 Dec 2006 23:19:54 -0800	[thread overview]
Message-ID: <891be9410612162319o7828c31ehc3bcf986a3ea991e@mail.gmail.com> (raw)
In-Reply-To: <20061217035307.GA32712@nevyn.them.org>

On 12/16/06, Daniel Jacobowitz <drow@false.org> wrote:
> 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.

Like I said, I did add some debugging code to softmmu_template.h. The
read/writes I'm seeing are being generated by that softmmu debugging
code, not the iommu code. Sorry if I wasn't clear. Is there some other
softmmu code I should be looking at?

> It may be easiest to add some new instrumentation in the translation
> code for whatever target you're interested in.

I'm just focusing on Linux i386. I'm only beginning to explore the
qemu source, so any pointer to files/functions I should look at will
be much appreciated!

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

  reply	other threads:[~2006-12-17  7:19 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
2006-12-17  7:19   ` Diwaker Gupta [this message]
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=891be9410612162319o7828c31ehc3bcf986a3ea991e@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).