From: "Andreas Färber" <afaerber@suse.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-1.6] memory: add tracepoints for MMIO reads/writes
Date: Sun, 28 Jul 2013 14:58:46 +0200 [thread overview]
Message-ID: <51F51586.2020305@suse.de> (raw)
In-Reply-To: <51F514C1.3030003@redhat.com>
Am 28.07.2013 14:55, schrieb Paolo Bonzini:
> Il 28/07/2013 14:45, Andreas Färber ha scritto:
>> Am 28.07.2013 14:35, schrieb Paolo Bonzini:
>>> 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"
>>
>> %u would seem more correct for unsigned - if you fix that, Reviewed-by:
>> Andreas Färber <afaerber@suse.de> and ACK that's it's good for 1.6.
>
> Ok, though it can only be 1/2/4/8.
I had static analysis in mind. ;)
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-07-28 12:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-28 12:35 [Qemu-devel] [PATCH for-1.6] memory: add tracepoints for MMIO reads/writes Paolo Bonzini
2013-07-28 12:45 ` Andreas Färber
2013-07-28 12:55 ` Paolo Bonzini
2013-07-28 12:58 ` Andreas Färber [this message]
2013-07-28 14:34 ` Peter Maydell
2013-07-28 15:02 ` Andreas Färber
2013-08-05 15:18 ` Don Slutz
2013-08-05 16:20 ` Paolo Bonzini
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=51F51586.2020305@suse.de \
--to=afaerber@suse.de \
--cc=pbonzini@redhat.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.