qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Harsh Bora <harsh@linux.vnet.ibm.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org, aneesh.kumar@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [RFC PATCH 0/2] Replace 9p debug infrastructure with Qemu Tracing
Date: Fri, 30 Sep 2011 16:26:37 +0530	[thread overview]
Message-ID: <4E85A065.4070802@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110929171651.GA1624@stefanha-thinkpad.localdomain>

On 09/29/2011 10:46 PM, Stefan Hajnoczi wrote:
> On Thu, Sep 29, 2011 at 06:09:47PM +0530, Harsh Prateek Bora wrote:
>> 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
>
> Reviewed-by: Stefan Hajnoczi<stefanha@linux.vnet.ibm.com>
>
> It would also be neat to wire up 9p pdu's to the pcap code in net/dump.c
> so it's possible to capture 9p sessions and look at them with wireshark.

Thanks Stefan for a quick response. I have sent a v2 for this patch 
incorporating aneesh's review comments with an additional patch to 
provide an analysis python script. I shall look into pcap code sometime 
soon.

Harsh

>
> Stefan
>

      reply	other threads:[~2011-09-30 10:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-29 12:39 [Qemu-devel] [RFC PATCH 0/2] Replace 9p debug infrastructure with Qemu Tracing Harsh Prateek Bora
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 [this message]

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=4E85A065.4070802@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).