public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Bird <tim.bird@am.sony.com>
To: "rostedt@goodmis.org" <rostedt@goodmis.org>
Cc: Tom Zanussi <tzanussi@gmail.com>, Ingo Molnar <mingo@elte.hu>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	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: Mon, 19 Apr 2010 13:39:09 -0700	[thread overview]
Message-ID: <4BCCBF6D.3030105@am.sony.com> (raw)
In-Reply-To: <1271707444.10448.12.camel@gandalf.stny.rr.com>

On 04/19/2010 01:04 PM, Steven Rostedt wrote:
> Hi Tom,
> 
> Could you add a way to do a call to tracing_on() or tracing_off() via
> the filters. I would like to do something like:
> 
> 
> echo 'if (pid == 1234) traceoff' > events/sched/sched_wakeup/filter
> 
> Where, if the sched_wakeup event is hit with pid == 1234 it will turn
> tracing off.

Just a comment on the nomenclature.  In KFT I called
things like this "triggers".  I'm not sure what other
tracing systems call them.  I'm a little worried about
overloading the filtering abstraction with trigger
semantics.  (I like the idea of triggers, but it might
be better to control them with another pseudo-file for
clarity.)

I suppose both are a form of conditional execution.
Filtering has an implicit action of either 'trace this'
or 'don't trace this', while triggering usually has
an action, often explicit, to start or stop tracing.
However, since they both use the conditional testing,
it might be a pain to reproduce this code for a different
pseudo-file.

Just my 2 cents.
 -- Tim

=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Network Entertainment
=============================


  reply	other threads:[~2010-04-19 21:09 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 [this message]
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
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=4BCCBF6D.3030105@am.sony.com \
    --to=tim.bird@am.sony.com \
    --cc=chase.douglas@canonical.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --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