All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harsh Bora <harsh@linux.vnet.ibm.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 0/4] Tracing patches
Date: Thu, 19 Jul 2012 17:22:04 +0530	[thread overview]
Message-ID: <5007F4E4.2060008@linux.vnet.ibm.com> (raw)
In-Reply-To: <1342695173-32010-1-git-send-email-stefanha@linux.vnet.ibm.com>

On 07/19/2012 04:22 PM, Stefan Hajnoczi wrote:
> Simpletrace v2 has landed:
>   * Strings are now logged instead of their pointers
>   * Variable-length arguments allow for >6 trace event arguments
>
> Thanks to Harsh Prateek Bora for this improvement!

Thanks very much to Stefan Hajnoczi for his effective, detailed reviews 
without which it would have taken longer.

regards,
Harsh

>
> The following changes since commit dfe1ce5d80cba603bafaac91b239d683abe19cf7:
>
>    Merge remote-tracking branch 'kwolf/for-anthony' into staging (2012-07-18 14:44:50 -0500)
>
> are available in the git repository at:
>
>
>    git://github.com/stefanha/qemu.git tracing
>
> for you to fetch changes up to 90a147a275da3a432bdf00238ebf438eff1d2c1b:
>
>    Update simpletrace.py for new log format (2012-07-19 11:34:33 +0100)
>
> ----------------------------------------------------------------
> Alexey Kardashevskiy (1):
>        trace: added ability to comment out events in the list
>
> Harsh Prateek Bora (3):
>        monitor: remove unused do_info_trace
>        Simpletrace v2: Support multiple arguments, strings.
>        Update simpletrace.py for new log format
>
>   monitor.c                           |   16 ---
>   scripts/simpletrace.py              |  116 +++++++++------
>   scripts/tracetool/backend/simple.py |   90 +++++++++---
>   trace/control.c                     |    3 +
>   trace/simple.c                      |  271 ++++++++++++++++++++---------------
>   trace/simple.h                      |   40 ++++--
>   6 files changed, 340 insertions(+), 196 deletions(-)
>

  parent reply	other threads:[~2012-07-19 11:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19 10:52 [Qemu-devel] [PULL 0/4] Tracing patches Stefan Hajnoczi
2012-07-19 10:52 ` [Qemu-devel] [PATCH 1/4] trace: added ability to comment out events in the list Stefan Hajnoczi
2012-07-19 10:52 ` [Qemu-devel] [PATCH 2/4] monitor: remove unused do_info_trace Stefan Hajnoczi
2012-07-19 10:52 ` [Qemu-devel] [PATCH 3/4] Simpletrace v2: Support multiple arguments, strings Stefan Hajnoczi
2012-07-19 10:52 ` [Qemu-devel] [PATCH 4/4] Update simpletrace.py for new log format Stefan Hajnoczi
2012-07-19 11:52 ` Harsh Bora [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-12-18 14:47 [Qemu-devel] [PULL 0/4] Tracing patches Stefan Hajnoczi
2017-12-19 12:48 ` Peter Maydell
2017-01-16 13:44 Stefan Hajnoczi
2017-01-19 10:46 ` Peter Maydell
2016-03-31 12:35 Stefan Hajnoczi
2016-03-31 13:58 ` Peter Maydell
2016-01-07  9:13 Stefan Hajnoczi
2016-01-07 11:22 ` Peter Maydell
2014-01-27 14:53 Stefan Hajnoczi
2014-01-31 11:22 ` Peter Maydell
2013-05-03 12:01 Stefan Hajnoczi
2012-11-16 13:19 Stefan Hajnoczi
2011-10-03 11:30 Stefan Hajnoczi
2011-10-08 16:35 ` 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=5007F4E4.2060008@linux.vnet.ibm.com \
    --to=harsh@linux.vnet.ibm.com \
    --cc=aliguori@us.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 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.