Re: [Qemu-devel] [PATCH for-1.6] memory: add tracepoints for MMIO reads/writes

[Paolo Bonzini]

On 08/05/2013 05:18 PM, Don Slutz wrote:
> > diff --git a/trace-events b/trace-events
> > index 002df83..3e0dd74 100644
> > --- a/trace-events
> > +++ b/trace-events
> > @@ -1165,6 +1165,10 @@ kvm_vm_ioctl(int type, void *arg) "type %d, arg
> > %p"
> >   kvm_vcpu_ioctl(int cpu_index, int type, void *arg) "cpu_index %d,
> > type %d, arg %p"
> >   kvm_run_exit(int cpu_index, uint32_t reason) "cpu_index %d, reason %d"
> > +# memory.c
> > +memory_region_ops_read(void *mr, uint64_t addr, uint64_t value,
> > unsigned size) "mr %p addr %#"PRIx64" value %#"PRIx64" size %d"
> > +memory_region_ops_write(void *mr, uint64_t addr, uint64_t value,
> > unsigned size) "mr %p addr %#"PRIx64" value %#"PRIx64" size %d"
> > +
> Sorry about the late mail.  Did you mean to have the stderr trace text
> to be the same?

Yes, the name of the tracepoint should come before the text.

See scripts/tracetool/backend/stderr.py for the generator source code.

Paolo