From: Harsh Prateek Bora <harsh@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: stefanha@gmail.com, Harsh Prateek Bora <harsh@linux.vnet.ibm.com>,
aneesh.kumar@linux.vnet.ibm.com
Subject: [Qemu-devel] [RFC PATCH 0/2] Replace 9p debug infrastructure with Qemu Tracing
Date: Thu, 29 Sep 2011 18:09:47 +0530 [thread overview]
Message-ID: <1317299989-30571-1-git-send-email-harsh@linux.vnet.ibm.com> (raw)
This patchset introduces Qemu Tracing to 9p pdu handlers and removes the
existing debug infrastructure which becomes less meaningful after the
introduction of coroutines. Parallel operations creates a messy output and
filtering becomes difficult. With Qemu tracing in place, we can selectively
enable/disable trace-events and the trace log can be further filtered using
analysis scripts.
Harsh Prateek Bora (2):
Introduce tracing for 9p pdu handlers
Remove virtio-9p-debug.* infra since we are using Qemu Tracing now.
Makefile.objs | 2 +-
hw/9pfs/virtio-9p-debug.c | 646 ---------------------------------------------
hw/9pfs/virtio-9p-debug.h | 6 -
hw/9pfs/virtio-9p.c | 70 +++++-
trace-events | 47 ++++
5 files changed, 110 insertions(+), 661 deletions(-)
delete mode 100644 hw/9pfs/virtio-9p-debug.c
delete mode 100644 hw/9pfs/virtio-9p-debug.h
next reply other threads:[~2011-09-29 12:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 12:39 Harsh Prateek Bora [this message]
2011-09-29 12:39 ` [Qemu-devel] [PATCH 1/2] Introduce tracing for 9p pdu handlers Harsh Prateek Bora
2011-09-30 5:26 ` Aneesh Kumar K.V
2011-09-29 12:39 ` [Qemu-devel] [PATCH 2/2] Remove virtio-9p-debug.* infra since we are using Qemu Tracing now Harsh Prateek Bora
2011-09-30 5:29 ` Aneesh Kumar K.V
2011-09-29 17:16 ` [Qemu-devel] [RFC PATCH 0/2] Replace 9p debug infrastructure with Qemu Tracing Stefan Hajnoczi
2011-09-30 10:56 ` Harsh Bora
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=1317299989-30571-1-git-send-email-harsh@linux.vnet.ibm.com \
--to=harsh@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).