From: Stefan Hajnoczi <stefanha@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 3/3] trace: enable all events by default
Date: Thu, 11 Nov 2010 09:31:28 +0000 [thread overview]
Message-ID: <AANLkTik5eNSqcS0EAi2dZh5bPw2EpGWkH=8OO7fAoHyZ@mail.gmail.com> (raw)
In-Reply-To: <8739r8vpt0.fsf@ginnungagap.bsc.es>
On Wed, Nov 10, 2010 at 9:20 PM, Lluís <xscript@gmx.net> wrote:
> Blue Swirl writes:
>
>> On Wed, Nov 10, 2010 at 7:57 PM, Lluís <xscript@gmx.net> wrote:
>>> Blue Swirl writes:
>>>
>>>> On Wed, Nov 10, 2010 at 5:59 PM, Lluís <xscript@gmx.net> wrote:
>>>>> So, my patch is just a matter of having all events available _only_ when
>>>>> you use a backend other than "nop".
>>>
>>>> Then the default for simpletrace (and dtrace?) should also be disabled
>>>> initial state. If you have 1000 tracepoints automatically enabled at
>>>> start (with simpletrace, not nop), disabling all of them if you are
>>>> only interested in a few of them is difficult.
>>>
>>> That's how it is. The patch sets always ".state=0" in "simple", and
>>> "dtrace" just does not do anything unless you plug something into the
>>> probe (similarly with "ust").
>
>> Oh, I missed .state=0 part, it was also not mentioned in the
>> description. Then these changes should be OK.
>
> My fault. If these are to be merged I can cook up a new series with a
> more verbose description.
Jan Kiszka suggested a solution for the simple trace backend: have a
qemu -trace events=<file> command-line option that enables the trace
events listed in the file on startup. Then we can really get rid of
disable. On LTTng UST and SystemTap building with everything in is a
good default, the user must explicitly enable probes at runtime with
those trace backends anyway.
Currently .state = 0 makes the simple backend less usable since it's a
drag to manually enable trace events from the monitor every time.
Stefan
next prev parent reply other threads:[~2010-11-11 9:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 14:08 [Qemu-devel] [PATCH v2 1/3] trace: [ust] fix generation of 'trace.c' on events without args Lluís
2010-11-09 14:08 ` [Qemu-devel] [PATCH v2 2/3] trace: always use the "nop" backend on events with the "disable" keyword Lluís
2010-11-09 14:08 ` [Qemu-devel] [PATCH v2 3/3] trace: enable all events by default Lluís
2010-11-10 17:21 ` Blue Swirl
2010-11-10 17:59 ` Lluís
2010-11-10 18:22 ` Blue Swirl
2010-11-10 19:57 ` Lluís
2010-11-10 20:23 ` Blue Swirl
2010-11-10 21:20 ` Lluís
2010-11-11 9:31 ` Stefan Hajnoczi [this message]
2010-11-16 17:03 ` Stefan Hajnoczi
2010-11-17 12:04 ` Lluís
2010-11-09 14:17 ` [Qemu-devel] [PATCH v2 1/3] trace: [ust] fix generation of 'trace.c' on events without args 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='AANLkTik5eNSqcS0EAi2dZh5bPw2EpGWkH=8OO7fAoHyZ@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=qemu-devel@nongnu.org \
/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).