qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Lluís Vilanova" <vilanova@ac.upc.edu>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH v3 0/8] Rewrite tracetool using python modules
Date: Thu, 29 Mar 2012 18:16:31 +0100	[thread overview]
Message-ID: <20120329171631.GA20821@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <20120327194910.7241.47693.stgit@ginnungagap.bsc.es>

On Tue, Mar 27, 2012 at 09:49:12PM +0200, Lluís Vilanova wrote:
> A full rewrite of the tracetool script using per-format and per-backend modules,
> so that it's easier to read and extend it in the future.
> 
> Signed-off-by: Lluís Vilanova <vilanova@ac.upc.edu>
> ---
> NOTE: This series applies in current master, ignoring the "Rewrite tracetool
>       using python" series.
> 
> Changes in v3:
> 
> * Some minor fixes according to comments from Alon Levy:
> ** Fixed some rogue tabs.
> ** Fixed definition of '_SCRIPT' in "tracetool.py".
> ** Fixed some documentation.
> ** Defensively treat results from 'try_import' in 'get_list'.
> ** Fixed the no-arguments case in 'tracetool.backend.dtrace.d'.
> ** Fixed the commandline checks for the "stap" format.
> ** Added '__repr__' methods for both Event and Arguments objects.
> 
> 
> Changes in v2:
> 
> * Fixed a strange import error.
> * Add a pointer to 'tracetool.out' in the format and backend documentation.
> 
> Lluís Vilanova (8):
>       tracetool: Rewrite infrastructure as python modules
>       tracetool: Add module for the 'c' format
>       tracetool: Add module for the 'h' format
>       tracetool: Add support for the 'stderr' backend
>       tracetool: Add support for the 'simple' backend
>       tracetool: Add support for the 'ust' backend
>       tracetool: Add support for the 'dtrace' backend
>       tracetool: Add MAINTAINERS info
> 
> 
>  MAINTAINERS                           |    2 
>  Makefile.objs                         |    6 
>  Makefile.target                       |   13 -
>  configure                             |    4 
>  scripts/tracetool                     |  648 ---------------------------------
>  scripts/tracetool.py                  |  141 +++++++
>  scripts/tracetool/__init__.py         |  223 +++++++++++
>  scripts/tracetool/backend/__init__.py |  119 ++++++
>  scripts/tracetool/backend/dtrace.py   |  104 +++++
>  scripts/tracetool/backend/simple.py   |   60 +++
>  scripts/tracetool/backend/stderr.py   |   61 +++
>  scripts/tracetool/backend/ust.py      |  102 +++++
>  scripts/tracetool/format/__init__.py  |   96 +++++
>  scripts/tracetool/format/c.py         |   20 +
>  scripts/tracetool/format/d.py         |   20 +
>  scripts/tracetool/format/h.py         |   45 ++
>  scripts/tracetool/format/stap.py      |   20 +
>  17 files changed, 1025 insertions(+), 659 deletions(-)
>  delete mode 100755 scripts/tracetool
>  create mode 100755 scripts/tracetool.py
>  create mode 100644 scripts/tracetool/__init__.py
>  create mode 100644 scripts/tracetool/backend/__init__.py
>  create mode 100644 scripts/tracetool/backend/dtrace.py
>  create mode 100644 scripts/tracetool/backend/simple.py
>  create mode 100644 scripts/tracetool/backend/stderr.py
>  create mode 100644 scripts/tracetool/backend/ust.py
>  create mode 100644 scripts/tracetool/format/__init__.py
>  create mode 100644 scripts/tracetool/format/c.py
>  create mode 100644 scripts/tracetool/format/d.py
>  create mode 100644 scripts/tracetool/format/h.py
>  create mode 100644 scripts/tracetool/format/stap.py

Only one point: please don't introduce PUBLIC yet.  Let's add it when
it's needed.  At the moment nothing uses it.

I have tested this series with all backends and looked at the diff
between the old tracetool and tracetool.py.

I'm happy with this series.  We need to test it hard for 1.1 to make
sure there are no hickups for tracing users.

Stefan

  parent reply	other threads:[~2012-03-29 18:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27 19:49 [Qemu-devel] [RFC PATCH v3 0/8] Rewrite tracetool using python modules Lluís Vilanova
2012-03-27 19:49 ` [Qemu-devel] [RFC PATCH v3 1/8] tracetool: Rewrite infrastructure as " Lluís Vilanova
2012-03-30  7:27   ` Stefan Hajnoczi
2012-03-30 16:55     ` Lluís Vilanova
2012-04-02  7:36       ` Stefan Hajnoczi
2012-04-02 12:57         ` Lluís Vilanova
2012-03-27 19:49 ` [Qemu-devel] [RFC PATCH v3 2/8] tracetool: Add module for the 'c' format Lluís Vilanova
2012-03-27 19:49 ` [Qemu-devel] [RFC PATCH v3 3/8] tracetool: Add module for the 'h' format Lluís Vilanova
2012-03-27 19:49 ` [Qemu-devel] [RFC PATCH v3 4/8] tracetool: Add support for the 'stderr' backend Lluís Vilanova
2012-03-27 19:49 ` [Qemu-devel] [RFC PATCH v3 5/8] tracetool: Add support for the 'simple' backend Lluís Vilanova
2012-03-27 19:49 ` [Qemu-devel] [RFC PATCH v3 6/8] tracetool: Add support for the 'ust' backend Lluís Vilanova
2012-03-27 19:49 ` [Qemu-devel] [RFC PATCH v3 7/8] tracetool: Add support for the 'dtrace' backend Lluís Vilanova
2012-03-27 19:49 ` [Qemu-devel] [RFC PATCH v3 8/8] tracetool: Add MAINTAINERS info Lluís Vilanova
2012-03-29 17:16 ` Stefan Hajnoczi [this message]
2012-03-30 17:12   ` [Qemu-devel] [RFC PATCH v3 0/8] Rewrite tracetool using python modules Lluís Vilanova
2012-04-02  7:39     ` Stefan Hajnoczi
2012-04-02 12:52       ` Lluís Vilanova
2012-04-02 13:16         ` Stefan Hajnoczi

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=20120329171631.GA20821@stefanha-thinkpad.localdomain \
    --to=stefanha@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=vilanova@ac.upc.edu \
    /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).