All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lluís Vilanova" <vilanova@ac.upc.edu>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 7/8] trace: [simple] Bump up log version number
Date: Wed, 12 Mar 2014 15:42:19 +0100	[thread overview]
Message-ID: <87fvmneawk.fsf@fimbulvetr.bsc.es> (raw)
In-Reply-To: <20140312141737.GB903@stefanha-thinkpad.muc.redhat.com> (Stefan Hajnoczi's message of "Wed, 12 Mar 2014 15:17:37 +0100")

Stefan Hajnoczi writes:

> On Sun, Feb 23, 2014 at 08:37:35PM +0100, Lluís Vilanova wrote:
>> The following tracetool cleanup changes the event numbering policy.
>> 
>> Signed-off-by: Lluís Vilanova <vilanova@ac.upc.edu>
>> ---
>> scripts/simpletrace.py |   10 +++++-----
>> trace/simple.c         |    2 +-
>> 2 files changed, 6 insertions(+), 6 deletions(-)

> I would also like to add a change to the simpletrace binary format.  The
> 32-bit reserved field will take the pid of QEMU.  I will also submit a
> SystemTap script that produces simpletrace binary format output - this
> allows us to produce simpletrace-compatible data with a QEMU binary that
> only has SystemTap support.  Since SystemTap is global it sees all QEMU
> processes and we need to distinguish between them using the pid.

> Your series will be merged into qemu.git at the start of the QEMU 2.1
> release cycle.  My patch can follow during the release cycle.  End-users
> will not see the changes until QEMU 2.1 is released.

Sounds excellent, but note that I also wrote a patch for multi-backend tracing
based on Kazuya's idea (must be applied on top of this series). Not sure if that
would influence your decision about SystemTap's format (since you could then
have both compiled into QEMU).

I will later send the latest version (rebased on this series).


Thanks,
  Lluis

-- 
 "And it's much the same thing with knowledge, for whenever you learn
 something new, the whole world becomes that much richer."
 -- The Princess of Pure Reason, as told by Norton Juster in The Phantom
 Tollbooth

  reply	other threads:[~2014-03-12 14:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-23 19:36 [Qemu-devel] [PATCH 0/8] Tracetool cleanup Lluís Vilanova
2014-02-23 19:37 ` [Qemu-devel] [PATCH 1/8] trace: [tracetool] Add method 'Event.api' to build event names Lluís Vilanova
2014-02-23 19:37 ` [Qemu-devel] [PATCH 2/8] trace: [tracetool] Add methods 'Event.copy' and 'Arguments.copy' Lluís Vilanova
2014-02-23 19:37 ` [Qemu-devel] [PATCH 3/8] trace: [tracetool] Spacing changes Lluís Vilanova
2014-02-23 19:37 ` [Qemu-devel] [PATCH 4/8] trace: [tracetool] Cosmetic changes Lluís Vilanova
2014-02-23 19:37 ` [Qemu-devel] [PATCH 5/8] trace: [tracetool] Show list of frontends and backends sorted by name Lluís Vilanova
2014-02-23 19:37 ` [Qemu-devel] [PATCH 6/8] trace: [tracetool] Change format docs to point to the generated file Lluís Vilanova
2014-02-23 19:37 ` [Qemu-devel] [PATCH 7/8] trace: [simple] Bump up log version number Lluís Vilanova
2014-03-12 14:17   ` Stefan Hajnoczi
2014-03-12 14:42     ` Lluís Vilanova [this message]
2014-03-14  9:02       ` Stefan Hajnoczi
2014-02-23 19:37 ` [Qemu-devel] [PATCH 8/8] trace: [tracetool] Minimize the amount of per-backend code Lluís Vilanova
2014-03-12 13:51 ` [Qemu-devel] [PATCH 0/8] Tracetool cleanup Lluís Vilanova
2014-03-12 14:13 ` 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=87fvmneawk.fsf@fimbulvetr.bsc.es \
    --to=vilanova@ac.upc.edu \
    --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.