From: "Lluís Vilanova" <vilanova@ac.upc.edu>
To: Jayanto Minocha <jayanto@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Tracing guest virtual addresses
Date: Tue, 20 Jun 2017 14:02:02 +0300 [thread overview]
Message-ID: <8760fqorbp.fsf@frigg.lan> (raw)
In-Reply-To: <CADR1n+V8R1LOGzbwdBDt5axeZ0mqh=WSCsfUo0Vr2nmE6BYqTQ@mail.gmail.com> (Jayanto Minocha's message of "Mon, 19 Jun 2017 14:15:21 -0700")
Jayanto Minocha writes:
> Hi,
> I think there have been a few threads on the mailing list regarding tracing
> guest virtual addresses for load and store instructions, but I have been
> unable to get it to work. I am trying this for an AArch64 machine, and am
> using the softmmu.
> The tracing infrastructure provides the following event:
> vcpu tcg guest_mem_before(...).
> But that is only used to instrument the cpu_ld/cpu_st macros, which is only
> called in the case of a tlb miss.
> I've been going over the archives, and it looks like I need to instrument
> tcg_out_tlb_load. Am I on the right path ?
That event should trace all guest memory accesses performed by the CPU. If you
found any case where this does not hold, it is likely a bug and I'd appreciate
it if you can point me to the smallest possible failing example.
Thanks,
Lluis
next prev parent reply other threads:[~2017-06-20 11:02 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 [this message]
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
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=8760fqorbp.fsf@frigg.lan \
--to=vilanova@ac.upc.edu \
--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 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.