All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Harsh Prateek Bora <harsh@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Cc: stefanha@gmail.com
Subject: Re: [Qemu-devel] [PATCH v2 0/3] Replace 9p debug infrastructure with Qemu Tracing
Date: Sat, 01 Oct 2011 15:10:18 +0530	[thread overview]
Message-ID: <87k48p2got.fsf@skywalker.in.ibm.com> (raw)
In-Reply-To: <1317378975-25080-1-git-send-email-harsh@linux.vnet.ibm.com>

On Fri, 30 Sep 2011 16:06:12 +0530, Harsh Prateek Bora <harsh@linux.vnet.ibm.com> wrote:
> This patchset introduces Qemu Tracing to 9p pdu handlers and removes the
> existing debug infrastructure which became less meaningful after the
> introduction of coroutines. With the existing debug infra, 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 pretty-printed/filtered using an analysis
> script.
> 
> Harsh Prateek Bora (3):
>   hw/9pfs: Introduce tracing for 9p pdu handlers
>   hw/9pfs: Remove virtio-9p-debug.* infra to be replaced by Qemu
>     Tracing.
>   scripts: Simpletrace log analysis script for pretty-printing 9p log.
> 

applied to v9fs tree with sample output added to patch 3

thanks
-aneesh

      parent reply	other threads:[~2011-10-01  9:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-30 10:36 [Qemu-devel] [PATCH v2 0/3] Replace 9p debug infrastructure with Qemu Tracing Harsh Prateek Bora
2011-09-30 10:36 ` [Qemu-devel] [PATCH v2 1/3] hw/9pfs: Introduce tracing for 9p pdu handlers Harsh Prateek Bora
2011-09-30 10:36 ` [Qemu-devel] [PATCH v2 2/3] hw/9pfs: Remove virtio-9p-debug.* infra to be replaced by Qemu Tracing Harsh Prateek Bora
2011-09-30 10:36 ` [Qemu-devel] [PATCH v2 3/3] scripts: Simpletrace log analysis script for pretty-printing 9p log Harsh Prateek Bora
2011-09-30 10:45   ` Harsh Bora
2011-10-01  9:40 ` Aneesh Kumar K.V [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=87k48p2got.fsf@skywalker.in.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=harsh@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 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.