From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>, William Cohen <wcohen@redhat.com>
Subject: [Qemu-devel] [PATCH 0/4] Remove trailing double quote limitation and add virtio_set_status trace event
Date: Tue, 13 Sep 2011 13:34:33 +0100 [thread overview]
Message-ID: <1315917277-20670-1-git-send-email-stefanha@linux.vnet.ibm.com> (raw)
This series removes the tracetool parser limitation that format strings must
begin and end with double quotes. In practice this means we need to work
around PRI*64 usage by adding dummy "" at the end of the line. It's fairly
easy to solve this parser limitation and do away with the workarounds.
While we're at it, also add the virtio_set_status() trace event to properly
follow the lifecycle of virtio devices.
docs/tracing.txt | 5 +----
hw/virtio.c | 10 ++++++++++
hw/virtio.h | 9 +--------
scripts/tracetool | 20 +++++++++++++-------
trace-events | 37 +++++++++++++++++++------------------
5 files changed, 44 insertions(+), 37 deletions(-)
next reply other threads:[~2011-09-13 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 12:34 Stefan Hajnoczi [this message]
2011-09-13 12:34 ` [Qemu-devel] [PATCH 1/4] trace: remove newline from grlib_irqmp_check_irqs format string Stefan Hajnoczi
2011-09-13 12:34 ` [Qemu-devel] [PATCH 2/4] trace: allow PRI*64 at beginning and ending of " Stefan Hajnoczi
2011-09-13 12:34 ` [Qemu-devel] [PATCH 3/4] trace: remove trailing double quotes after PRI*64 Stefan Hajnoczi
2011-09-13 12:34 ` [Qemu-devel] [PATCH 4/4] trace: add virtio_set_status() trace event Stefan Hajnoczi
2011-09-17 18:49 ` [Qemu-devel] [PATCH 0/4] Remove trailing double quote limitation and add virtio_set_status " Blue Swirl
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=1315917277-20670-1-git-send-email-stefanha@linux.vnet.ibm.com \
--to=stefanha@linux.vnet.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=wcohen@redhat.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).