From: Steven Rostedt <rostedt@goodmis.org>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>,
Rusty Russell <rusty@rustcorp.com.au>,
chris <chris@chris-wilson.co.uk>
Subject: Re: [PATCH][RFC] tracing: Enable tracepoints via module parameters
Date: Tue, 08 Mar 2011 21:12:14 -0500 [thread overview]
Message-ID: <1299636734.20306.134.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20110309020131.GA19224@yliu-dev.sh.intel.com>
On Wed, 2011-03-09 at 10:01 +0800, Yuanhan Liu wrote:
> > Users are for testing code ;)
>
> As another end-user, this looks fine (also simple) to me ;)
Ah, you find this patch I have simple?
>
> >
> > But that's a good question. As I wrote this because I'm purging my inbox
> > and came across Yuanhan Liu's patch set. I'm curios to what Yuanhan's
> > motivation for this change was.
>
> The motivation of my original patch is simple: try to not miss any trace
> events. I guess it's a kind of feature that trace(or module) should
> have ;)
Hmm, I probably could add a trace option that simply tells ftrace to
enable events as modules are loaded.
Thanks!
-- Steve
next prev parent reply other threads:[~2011-03-09 2:12 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 [this message]
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
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=1299636734.20306.134.camel@gandalf.stny.rr.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.