From: Stefan Hajnoczi <stefanha@gmail.com>
To: Lluís <xscript@gmx.net>
Cc: qemu-devel@nongnu.org, Fabien Chouteau <chouteau@adacore.com>,
Prerna Saxena <prerna@linux.vnet.ibm.com>
Subject: [Qemu-devel] Re: [RFC][PATCH 0/6] trace-state: make the behaviour of "disable" consistent across all backends
Date: Wed, 6 Apr 2011 12:42:59 +0100 [thread overview]
Message-ID: <BANLkTik3u+EHerFD-cbmLApuALsmp5wa_A@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikiR8DUEuiv88iXaK0wuEW_qKnWCA@mail.gmail.com>
On Tue, Apr 5, 2011 at 2:30 PM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Mon, Apr 4, 2011 at 10:49 PM, Lluís <xscript@gmx.net> wrote:
>> This patch defines the "disable" trace event state to always use the "nop"
>> backend.
>>
>> As a side-effect, all events are now enabled (without "disable") by default, as
>> all backends (except "stderr") have programmatic support for dynamically
>> (de)activating each trace event.
>>
>> In order to make this true, the "simple" backend now has a "-trace
>> events=<file>" argument to let the user select which events must be enabled from
>> the very beginning.
>>
>> Signed-off-by: Lluís Vilanova <vilanova@ac.upc.edu>
>> ---
>>
>> Lluís Vilanova (6):
>> trace: [ust] fix generation of 'trace.c' on events without args
>> trace: generalize the "property" concept in the trace-events file
>> trace-state: always use the "nop" backend on events with the "disable" keyword
>> trace-state: [simple] disable all trace points by default
>> trace-state: [simple] add "-trace events" argument to control initial state
>> trace: enable all events
>>
>>
>> docs/tracing.txt | 12 +-
>> qemu-config.c | 5 +
>> qemu-options.hx | 18 ++
>> scripts/tracetool | 88 +++++-------
>> trace-events | 385 ++++++++++++++++++++++++++---------------------------
>> vl.c | 94 ++++++++-----
>> 6 files changed, 313 insertions(+), 289 deletions(-)
>
> Excellent, thanks for implementing this. I'll review the patches in
> detail shortly.
I've left feedback on the individual patches. This is a nice cleanup,
thanks for doing this work!
The stderr backend is impacted - but not severely. You now need to
disable all trace events that should not generate output. Previously
it was the opposite; you needed to enable all trace events that should
generate output.
Adding Prerna (simpletrace) and Fabien (stderr) on CC so they can take a look.
I'd like to merge v2 into my tracing tree and send the qemu.git
maintainer a pull request soon.
Stefan
next prev parent reply other threads:[~2011-04-06 11:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 21:49 [Qemu-devel] [RFC][PATCH 0/6] trace-state: make the behaviour of "disable" consistent across all backends Lluís
2011-04-04 21:49 ` [Qemu-devel] [PATCH 1/6] trace: [ust] fix generation of 'trace.c' on events without args Lluís
2011-04-04 21:49 ` [Qemu-devel] [PATCH 2/6] trace: generalize the "property" concept in the trace-events file Lluís
2011-04-06 10:53 ` [Qemu-devel] " Stefan Hajnoczi
2011-04-04 21:49 ` [Qemu-devel] [PATCH 3/6] trace-state: always use the "nop" backend on events with the "disable" keyword Lluís
2011-04-06 11:04 ` [Qemu-devel] " Stefan Hajnoczi
2011-04-04 21:49 ` [Qemu-devel] [PATCH 4/6] trace-state: [simple] disable all trace points by default Lluís
2011-04-04 21:49 ` [Qemu-devel] [PATCH 5/6] trace-state: [simple] add "-trace events" argument to control initial state Lluís
2011-04-06 11:37 ` [Qemu-devel] " Stefan Hajnoczi
2011-04-06 14:15 ` Lluís
2011-04-06 20:30 ` Stefan Hajnoczi
2011-04-06 21:45 ` Lluís
2011-04-04 21:49 ` [Qemu-devel] [PATCH 6/6] trace: enable all events Lluís
2011-04-06 11:38 ` [Qemu-devel] " Stefan Hajnoczi
2011-04-05 13:30 ` [Qemu-devel] Re: [RFC][PATCH 0/6] trace-state: make the behaviour of "disable" consistent across all backends Stefan Hajnoczi
2011-04-06 11:42 ` Stefan Hajnoczi [this message]
2011-04-06 14:30 ` Fabien Chouteau
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=BANLkTik3u+EHerFD-cbmLApuALsmp5wa_A@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=chouteau@adacore.com \
--cc=prerna@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=xscript@gmx.net \
/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).