From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:41122)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <peter.maydell@linaro.org>) id 1Zuezg-0000xL-FR
	for qemu-devel@nongnu.org; Fri, 06 Nov 2015 06:15:45 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <peter.maydell@linaro.org>) id 1Zuezf-00024I-GO
	for qemu-devel@nongnu.org; Fri, 06 Nov 2015 06:15:44 -0500
Received: from mail-vk0-x233.google.com ([2607:f8b0:400c:c05::233]:34365)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <peter.maydell@linaro.org>) id 1Zuezf-00024E-39
	for qemu-devel@nongnu.org; Fri, 06 Nov 2015 06:15:43 -0500
Received: by vkgs66 with SMTP id s66so11782807vkg.1
	for <qemu-devel@nongnu.org>; Fri, 06 Nov 2015 03:15:42 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <20151106111203.GF12285@stefanha-x1.localdomain>
References: <56379ACB.3010905@mentor.com>
	<20151106111203.GF12285@stefanha-x1.localdomain>
From: Peter Maydell <peter.maydell@linaro.org>
Date: Fri, 6 Nov 2015 11:15:23 +0000
Message-ID: <CAFEAcA_n2vmrS4aPAEDm5EASCpRo5Z9FDNH1zAwdconFE5qDeA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [Qemu-devel] anybody using MMIO tracing?
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Hollis Blanchard <hollis_blanchard@mentor.com>, QEMU Developers <qemu-devel@nongnu.org>

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