Re: [Qemu-devel] anybody using MMIO tracing?

2015-11-13 Thread Stefan Hajnoczi
On Fri, Nov 06, 2015 at 09:47:45AM -0800, Hollis Blanchard wrote: > By the way, docs/tracing.txt says: > >The "simple" backend currently does not capture string arguments, it >simply >records the char* pointer value instead of the string that is >pointed to. > > This seems no

Re: [Qemu-devel] anybody using MMIO tracing?

2015-11-06 Thread Hollis Blanchard
On 11/06/2015 03:15 AM, Peter Maydell wrote: On 6 November 2015 at 11:12, Stefan Hajnoczi 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:

Re: [Qemu-devel] anybody using MMIO tracing?

2015-11-06 Thread Stefan Hajnoczi
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

Re: [Qemu-devel] anybody using MMIO tracing?

2015-11-06 Thread Peter Maydell
On 6 November 2015 at 11:12, Stefan Hajnoczi 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

[Qemu-devel] anybody using MMIO tracing?

2015-11-02 Thread Hollis Blanchard
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=0x size=0x4