From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <fweisbec@gmail.com>,
Darren Hart <dvhart@linux.intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"jason.wessel" <jason.wessel@windriver.com>,
"Ted Ts'o" <tytso@mit.edu>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [RFC][PATCH 0/2] tracing: Have trace_printk()s in the events/ directory
Date: Thu, 18 Nov 2010 11:41:06 +0100 [thread overview]
Message-ID: <1290076866.2109.1305.camel@laptop> (raw)
In-Reply-To: <20101118035803.453609353@goodmis.org>
On Wed, 2010-11-17 at 22:58 -0500, Steven Rostedt wrote:
> For example, I added a trace_printk() in kernel/sched.c at line 2180
> and it creates:
>
> # ls /debug/tracing/events/printk/kernel/sched.c/2180/
> enable format
>
> The format is the printk format:
>
> # cat /debug/tracing/events/printk/kernel/sched.c/2180/format
> "migrate task %s:%d"
*groan*, so you're creating a tracepoint per instance?
That's going to be massive pain for perf.. I really don't see the point
in splitting all that out.
next prev parent reply other threads:[~2010-11-18 10:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 3:58 [RFC][PATCH 0/2] tracing: Have trace_printk()s in the events/ directory Steven Rostedt
2010-11-18 3:58 ` [RFC][PATCH 1/2] [PATCH 1/2] tracing: Rename trace_printk to ftrace_printk Steven Rostedt
2010-11-18 3:58 ` [RFC][PATCH 2/2] [PATCH 2/2] tracing: Make event based trace_printk() Steven Rostedt
2010-11-18 4:19 ` Steven Rostedt
2010-11-18 5:50 ` Lai Jiangshan
2010-11-18 12:22 ` Steven Rostedt
2010-11-18 11:58 ` Mathieu Desnoyers
2010-11-18 12:14 ` Steven Rostedt
2010-11-18 10:41 ` Peter Zijlstra [this message]
2010-11-18 11:53 ` [RFC][PATCH 0/2] tracing: Have trace_printk()s in the events/ directory Steven Rostedt
2010-11-18 12:06 ` Mathieu Desnoyers
2010-11-18 12:14 ` Steven Rostedt
2010-11-18 13:03 ` Mathieu Desnoyers
2010-11-18 12:53 ` Frederic Weisbecker
2010-11-18 13:06 ` Steven Rostedt
2010-11-18 14:02 ` Frederic Weisbecker
2010-11-18 13:21 ` Peter Zijlstra
2010-11-18 13:36 ` Frederic Weisbecker
2010-11-18 12:39 ` Frederic Weisbecker
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=1290076866.2109.1305.camel@laptop \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dvhart@linux.intel.com \
--cc=fweisbec@gmail.com \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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