From: Steven Rostedt <rostedt@goodmis.org>
To: Tom Zanussi <tzanussi@gmail.com>
Cc: 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: request to add trace off and trace on with events
Date: Mon, 19 Apr 2010 16:04:04 -0400 [thread overview]
Message-ID: <1271707444.10448.12.camel@gandalf.stny.rr.com> (raw)
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.
I would also like to do just:
echo 'traceoff' > events/sched/sched_wakeup/filter
to disable tracing every time the event is hit.
Perhaps you can just add a call back where the kernel could register
something to be called if a command is used in the filter.
register_event_command("traceoff", trace_off_cb);
where the trace_off_cb is a function that is called by the event if the
traceoff command is hit. This would allow other commands to be added
later.
Would something like this be doable, I was looking at the code, and it
certain looks feasible, but it would take me longer to implement it than
it would you :-)
Thanks,
-- Steve
next reply other threads:[~2010-04-19 20:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 20:04 Steven Rostedt [this message]
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
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=1271707444.10448.12.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=chase.douglas@canonical.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®