From: Peter Maydell <peter.maydell@linaro.org>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Hollis Blanchard <hollis_blanchard@mentor.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] anybody using MMIO tracing?
Date: Fri, 6 Nov 2015 11:15:23 +0000 [thread overview]
Message-ID: <CAFEAcA_n2vmrS4aPAEDm5EASCpRo5Z9FDNH1zAwdconFE5qDeA@mail.gmail.com> (raw)
In-Reply-To: <20151106111203.GF12285@stefanha-x1.localdomain>
On 6 November 2015 at 11:12, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Mon, Nov 02, 2015 at 09:18:03AM -0800, Hollis Blanchard wrote:
>> I'm trying to use the memory_region_ops_read/write tracepoints. They produce
>> output like this:
>>
>> memory_region_ops_write 0.000 pid=8861 mr=0x185b1e8 addr=0x0
>> value=0x3 size=0x4
>> memory_region_ops_write 165.000 pid=8861 mr=0x185b1e8 addr=0x80
>> value=0xffffffff size=0x4
>> memory_region_ops_write 155.000 pid=8861 mr=0x1914240 addr=0x0
>> value=0x3 size=0x4
>> memory_region_ops_write 2.000 pid=8861 mr=0x185b320 addr=0x0
>> value=0x3 size=0x4
>> memory_region_ops_write 134.000 pid=8861 mr=0x1914240 addr=0x4
>> value=0x80 size=0x4
>>
>> How do I discover which devices are represented by MemoryRegions 0x185b1e8
>> and 0x1914240? Or alternatively how do I discover the full addresses?
>
> As a KVM user I use the kvm:kvm_mmio and kvm:kvm_pio kernel trace
> events.
Is there a reason why we can't print the mr->name in this tracing?
thanks
-- PMM
next prev parent reply other threads:[~2015-11-06 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 17:18 [Qemu-devel] anybody using MMIO tracing? Hollis Blanchard
2015-11-06 11:12 ` Stefan Hajnoczi
2015-11-06 11:15 ` Peter Maydell [this message]
2015-11-06 17:47 ` Hollis Blanchard
2015-11-13 9:33 ` Stefan Hajnoczi
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=CAFEAcA_n2vmrS4aPAEDm5EASCpRo5Z9FDNH1zAwdconFE5qDeA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=hollis_blanchard@mentor.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).