From: maestro <maestro82@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Tracing memory accesses by emulated systems
Date: Sun, 04 Feb 2007 19:43:34 +0100 [thread overview]
Message-ID: <1170614615.2110.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20070204161752.GA7610@core>
Am Sonntag, den 04.02.2007, 17:17 +0100 schrieb Christian Leber:
> Hello,
>
> I would like to trace all "physical" memory read/write operations for x86_64,
> but I have to admit that I'm not sure where exactly this has to be
> implemented.
>
> Could somebody give me some hints where and how I could do that?
> (or is there already a patch that does this? on irc somebody suggested
> that something like that could exist, but I was not able to find it)
>
> Regards
>
> Christian Leber
hello christian!
i'm not sure if it applies for 64bit (but i'd assume it does).
afaik the easiest way to catch "all" (dma operations are not covered
there - i think) memory accesses is via the ld*,st* macros in
softmmu_helper.h and softmmu_header.h. at least this is the way i did
that.
cheers
m.
prev parent reply other threads:[~2007-02-04 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-04 16:17 [Qemu-devel] Tracing memory accesses by emulated systems Christian Leber
2007-02-04 18:43 ` maestro [this message]
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=1170614615.2110.3.camel@localhost.localdomain \
--to=maestro82@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.