From: "Emilio G. Cota" <cota@braap.org>
To: Jayanto Minocha <jayanto@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Tracing guest virtual addresses
Date: Mon, 26 Jun 2017 13:42:08 -0400 [thread overview]
Message-ID: <20170626174208.GA17935@flamenco> (raw)
In-Reply-To: <87zicwgt3l.fsf@frigg.lan>
On Sun, Jun 25, 2017 at 15:16:46 +0300, Lluís Vilanova wrote:
> Lluís Vilanova writes:
>
> > Jayanto Minocha writes:
> >> Lluis,
> >> My modifications were almost the same as those done by Emilio. There were
> >> no memory trace events in the trace file.
>
> > I'll take a look at it after I finish revamping the generic translation loop
> > series (hopefully today).
>
> I just sent a patch that should fix it:
>
> https://lists.gnu.org/archive/html/qemu-devel/2017-06/msg05491.html
Yay! That fixes the problem for me:
$ ../scripts/simpletrace.py trace-events-all trace-17579 | head -5
guest_mem_before_exec 0.000 pid=17579 __cpu=0x563780e726a0 vaddr=0x4000a2a030 info=0x4
guest_mem_before_exec 0.368 pid=17579 __cpu=0x563780e726a0 vaddr=0x4000a2a034 info=0x4
guest_mem_before_exec 0.162 pid=17579 __cpu=0x563780e726a0 vaddr=0x4000a2a034 info=0x14
guest_mem_before_exec 0.163 pid=17579 __cpu=0x563780e726a0 vaddr=0x4000a2a028 info=0x4
guest_mem_before_exec 0.109 pid=17579 __cpu=0x563780e726a0 vaddr=0x4000a2a02c info=0x4
Thanks,
Emilio
prev parent reply other threads:[~2017-06-26 17:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 21:15 [Qemu-devel] Tracing guest virtual addresses Jayanto Minocha
2017-06-20 11:02 ` Lluís Vilanova
2017-06-20 11:13 ` Peter Maydell
2017-06-21 14:44 ` Alex Bennée
2017-06-25 12:20 ` Lluís Vilanova
2017-06-25 17:35 ` Alex Bennée
2017-06-26 9:26 ` Lluís Vilanova
2017-06-26 9:32 ` Peter Maydell
2017-06-26 12:04 ` Lluís Vilanova
2017-06-26 12:14 ` Peter Maydell
2017-06-20 17:20 ` Emilio G. Cota
2017-06-20 22:30 ` Jayanto Minocha
2017-06-22 5:36 ` Lluís Vilanova
2017-06-25 12:16 ` Lluís Vilanova
2017-06-26 17:42 ` Emilio G. Cota [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=20170626174208.GA17935@flamenco \
--to=cota@braap.org \
--cc=jayanto@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).