From: Steven Rostedt <rostedt@goodmis.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>,
Yuanhan Liu <yuanhan.liu@linux.intel.com>,
chris <chris@chris-wilson.co.uk>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH][RFC] tracing: Enable tracepoints via module parameters
Date: Wed, 14 Aug 2013 23:32:28 -0400 [thread overview]
Message-ID: <20130814233228.778f25d0@gandalf.local.home> (raw)
In-Reply-To: <87siybk8yl.fsf@rustcorp.com.au>
On Thu, 15 Aug 2013 11:32:10 +0930
Rusty Russell <rusty@rustcorp.com.au> wrote:
> Steven Rostedt <rostedt@goodmis.org> writes:
> > But the thing about this that bothers me is that there's no way to say,
> > "Enable all tracepoints in this module on load". I would like a way to
> > do that, but I don't know of a way to do that without modifying the
> > module code. Have any ideas? Basically, I would love to have:
> >
> > insmod foo tracepoints=all
> >
> > or something and have all tracepoints enabled.
>
> "without modifying the module code"? Why? The code isn't that scary,
> and this seems useful.
I'm not afraid of the code, I'm afraid of you ;-) I hear you have
killer puppies.
OK, then when I get some time, I may cook something up.
Thanks,
-- Steve
next prev parent reply other threads:[~2013-08-15 3:32 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 22:18 [PATCH][RFC] tracing: Enable tracepoints via module parameters Steven Rostedt
2011-03-08 22:42 ` Steven Rostedt
2011-03-08 23:22 ` Mathieu Desnoyers
2011-03-08 23:32 ` Steven Rostedt
2011-03-09 0:07 ` Mathieu Desnoyers
2011-03-09 0:14 ` Steven Rostedt
2011-03-09 0:29 ` Mathieu Desnoyers
2011-03-09 0:52 ` Steven Rostedt
2011-03-09 1:17 ` Mathieu Desnoyers
2011-03-09 2:01 ` Steven Rostedt
2011-03-09 2:30 ` Mathieu Desnoyers
2011-03-09 2:01 ` Yuanhan Liu
2011-03-09 2:12 ` Steven Rostedt
2011-03-09 2:19 ` Yuanhan Liu
2011-03-10 23:33 ` Rusty Russell
2013-08-13 15:14 ` Steven Rostedt
2013-08-13 22:34 ` Mathieu Desnoyers
2013-08-13 23:09 ` Steven Rostedt
2013-08-15 2:02 ` Rusty Russell
2013-08-15 3:32 ` Steven Rostedt [this message]
2021-04-19 21:54 ` Williams, Dan J
2021-04-19 22:11 ` Steven Rostedt
2021-04-20 1:25 ` Dan Williams
2021-04-20 12:55 ` Steven Rostedt
2021-04-20 13:29 ` Mathieu Desnoyers
2021-04-20 14:55 ` Steven Rostedt
2021-04-20 15:15 ` Mathieu Desnoyers
2021-04-20 15:34 ` Steven Rostedt
2021-04-20 19:54 ` Dan Williams
2021-04-20 20:32 ` Steven Rostedt
2021-04-21 6:27 ` Dan Williams
2021-04-21 7:30 ` Rasmus Villemoes
2021-04-21 14:20 ` Steven Rostedt
2021-04-21 14:50 ` Rasmus Villemoes
2021-04-21 15:00 ` Steven Rostedt
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=20130814233228.778f25d0@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=chris@chris-wilson.co.uk \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=yuanhan.liu@linux.intel.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;
as well as URLs for NNTP newsgroup(s).