From: Frederic Weisbecker <fweisbec@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Tim Bird <tim.bird@am.sony.com>, Tom Zanussi <tzanussi@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Chase Douglas <chase.douglas@canonical.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: request to add trace off and trace on with events
Date: Tue, 20 Apr 2010 00:04:39 +0200 [thread overview]
Message-ID: <20100419220437.GC8811@nowhere> (raw)
In-Reply-To: <1271713074.10448.101.camel@gandalf.stny.rr.com>
On Mon, Apr 19, 2010 at 05:37:54PM -0400, Steven Rostedt wrote:
> On Mon, 2010-04-19 at 23:29 +0200, Frederic Weisbecker wrote:
>
> > The problem with having triggers defined in the filter file is that
> > you couldn't set a normal filter plus a trigger.
> >
> > That said a filter itself could be a trigger.
> >
> > if (cond) filter
> >
> > This is going to break some ABI though.
> >
> > In fact having one file per trigger type is going to make the
> > things much easier if you don't want to encumber with syntax parsing,
> > and just reuse the filtering code as is with very few modification.
> > This is going to be also easier for the users as they don't have to
> > remember the syntax or the available triggers.
> >
> > Say you are in an event directory:
> >
> > $ ls triggers/
> >
> > filter
> > tracing_off
> > tracing_on
> > dump_trace
> >
> > $ echo "(a == 1 && b == 2)" > tracing_off
> >
> > So in the above example, you just reuse the filtering code,
> > no need to parse an if or a command.
> > The filter becomes a command. I've listed it in the triggers
> > directory but this just to express the fact it can be treated
> > like whatever trigger command, this is just an implementation
> > POV. In fact we can just keep it in the event directory.
>
>
> I like this. Heck, all registered triggers can be shown here.
>
> # cat event/sched/sched_switch/triggers/tracing_off
> disabled
>
> Or it can be a filter, or enabled.
Yep, since it would share exatly the same code than filter (as
filter basically becomes a trigger command), it can behave the
same: displaying "none" when there is no filter, or a filter.
>
> This could also allow a user to do:
>
> echo "(a > 100)" > tracing_on
> echo "(a < 100)" > tracing_off
Yeah :)
But if the scope of the "tracing off" is only for this event, then
rather use:
echo "(a < 100)" > filter
You could have tracing_off/on that have this event scope and
tracing_off/on_all for a global tracing scope.
next prev parent reply other threads:[~2010-04-19 22:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 20:04 request to add trace off and trace on with events Steven Rostedt
2010-04-19 20:39 ` Tim Bird
2010-04-19 20:44 ` Steven Rostedt
2010-04-19 20:56 ` Tim Bird
2010-04-19 21:10 ` Steven Rostedt
2010-04-19 21:32 ` Tim Bird
2010-04-19 21:29 ` Frederic Weisbecker
2010-04-19 21:37 ` Steven Rostedt
2010-04-19 22:04 ` Frederic Weisbecker [this message]
2010-04-19 22:13 ` Steven Rostedt
2010-04-19 23:04 ` Frederic Weisbecker
2010-04-19 23:59 ` Steven Rostedt
2010-04-20 6:52 ` Tom Zanussi
2010-04-20 5:07 ` Tom Zanussi
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=20100419220437.GC8811@nowhere \
--to=fweisbec@gmail.com \
--cc=chase.douglas@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tim.bird@am.sony.com \
--cc=tzanussi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox