qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jun Koi <junkoi2004@gmail.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] memory trace with qemu
Date: Fri, 23 Jul 2010 16:34:53 +0900	[thread overview]
Message-ID: <AANLkTikNVZdYTaLC15f7WDOQSYy1eU7P8DA4RjzgzxDq@mail.gmail.com> (raw)
In-Reply-To: <AANLkTili9UdnzkpKh-YBhARzI-1NWewuvf1b3pH-5Zd9@mail.gmail.com>

On Fri, Jul 23, 2010 at 3:15 PM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Fri, Jul 23, 2010 at 4:12 AM, Mulyadi Santosa
> <mulyadi.santosa@gmail.com> wrote:
>> Hi...
>>
>> On Fri, Jul 23, 2010 at 05:30, Eduardo Cruz <eduardohmdacruz@gmail.com> wrote:
>>> Hello, I need qemu to keep track of all the memory access made by the guest,
>>> including read, write and the instruction fetches.
>>
>> AFAIK there are lots of experiments on this and has produces working
>> patches...at least from the posting of the creator. There is even a
>> patch floating to start creating trace framework a while ago.
>
> Thanks Mulyadi, I think you are referring to the tracing work that
> Prerna Saxena and I are doing.  Here is the documentation:
>
> http://repo.or.cz/w/qemu/stefanha.git/blob/tracing:/docs/tracing.txt
>
> The patches apply to qemu.git.  You can define trace events in the
> trace-events file and then call them from places in the code.  There
> is a script to pretty-print the binary trace file that QEMU produces.
>

what trace events do you support now?

thanks,
J

  parent reply	other threads:[~2010-07-23  7:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-22 22:30 [Qemu-devel] memory trace with qemu Eduardo Cruz
2010-07-23  3:12 ` Mulyadi Santosa
2010-07-23  6:15   ` Stefan Hajnoczi
2010-07-23  7:25     ` Mulyadi Santosa
2010-07-23  8:39       ` Stefan Hajnoczi
2010-07-23 19:24         ` Mulyadi Santosa
2010-07-23  7:34     ` Jun Koi [this message]
2010-07-23  8:43       ` Stefan Hajnoczi
2010-07-24  2:17     ` Yufei Chen
2010-07-24  9:05       ` Stefan Hajnoczi
2010-07-25 22:21         ` Eduardo Cruz
2010-07-26  2:05           ` Yufei Chen
2010-07-26 10:20           ` Lluís
2010-07-26 10:57             ` Eliot Moss
2010-07-26 11:16               ` malc
2010-07-26 12:41                 ` Lluís
2010-07-27  0:24                 ` Jun Koi
2010-07-27  6:46                   ` malc
2010-08-11 17:26                     ` Eduardo Cruz
2010-07-26 14:27             ` Yufei Chen
2010-07-26 17:32               ` Eduardo Cruz
2010-07-26 21:44                 ` Lluís
2010-07-26 22:16                   ` Eduardo Cruz

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=AANLkTikNVZdYTaLC15f7WDOQSYy1eU7P8DA4RjzgzxDq@mail.gmail.com \
    --to=junkoi2004@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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).