From: Avi Kivity <avi@redhat.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
Prerna Saxena <prerna@linux.vnet.ibm.com>
Subject: [Qemu-devel] Re: [PATCH 7/7] trace: Trace virtqueue operations
Date: Tue, 25 May 2010 15:04:19 +0300 [thread overview]
Message-ID: <4BFBBCC3.2080905@redhat.com> (raw)
In-Reply-To: <1274783056-14759-8-git-send-email-stefanha@linux.vnet.ibm.com>
On 05/25/2010 01:24 PM, Stefan Hajnoczi wrote:
> This patch adds trace events for virtqueue operations including
> adding/removing buffers, notifying the guest, and receiving a notify
> from the guest.
>
> diff --git a/trace-events b/trace-events
> index 48415f8..a533414 100644
> --- a/trace-events
> +++ b/trace-events
> @@ -35,6 +35,14 @@ qemu_memalign(size_t alignment, size_t size, void *ptr) "alignment %zu size %zu
> qemu_valloc(size_t size, void *ptr) "size %zu ptr %p"
> qemu_vfree(void *ptr) "ptr %p"
>
> +# hw/virtio.c
> +virtqueue_fill(void *vq, const void *elem, unsigned int len, unsigned int idx) "vq %p elem %p len %u idx %u"
> +virtqueue_flush(void *vq, unsigned int count) "vq %p count %u"
> +virtqueue_pop(void *vq, void *elem, unsigned int in_num, unsigned int out_num) "vq %p elem %p in_num %u out_num %u"
> +virtio_queue_notify(void *vdev, int n, void *vq) "vdev %p n %d vq %p"
> +virtio_irq(void *vq) "vq %p"
> +virtio_notify(void *vdev, void *vq) "vdev %p vq %p"
> +
>
Those %ps are more or less useless. We need better ways of identifying
them.
Linux uses %pTYPE to pretty print arbitrary types. We could do
something similar (not the same since we don't want our own printf
implementation).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-05-25 12:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 10:24 [Qemu-devel] [PATCH v2 0/7] Tracing backends Stefan Hajnoczi
2010-05-25 10:24 ` [Qemu-devel] [PATCH 1/7] trace: Add trace-events file for declaring trace events Stefan Hajnoczi
2010-06-08 6:34 ` [Qemu-devel] [PATCH] Re: Tracing backends : Fix for building with --prefix Prerna Saxena
2010-06-15 13:49 ` [Qemu-devel] " Stefan Hajnoczi
2010-05-25 10:24 ` [Qemu-devel] [PATCH 2/7] trace: Support disabled events in trace-events Stefan Hajnoczi
2010-05-25 10:24 ` [Qemu-devel] [PATCH 3/7] trace: Add simple built-in tracing backend Stefan Hajnoczi
2010-05-25 10:24 ` [Qemu-devel] [PATCH 4/7] trace: Add LTTng Userspace Tracer backend Stefan Hajnoczi
2010-05-25 10:24 ` [Qemu-devel] [PATCH 5/7] trace: Trace qemu_malloc() and qemu_vmalloc() Stefan Hajnoczi
2010-05-25 10:24 ` [Qemu-devel] [PATCH 6/7] trace: Trace virtio-blk, multiwrite, and paio_submit Stefan Hajnoczi
2010-05-25 10:24 ` [Qemu-devel] [PATCH 7/7] trace: Trace virtqueue operations Stefan Hajnoczi
2010-05-25 12:04 ` Avi Kivity [this message]
2010-05-25 13:27 ` [Qemu-devel] " Stefan Hajnoczi
2010-05-25 13:52 ` Avi Kivity
2010-05-25 14:00 ` 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=4BFBBCC3.2080905@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=prerna@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).