[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1290076866.2109.1305.camel@laptop>
Date: Thu, 18 Nov 2010 11:41:06 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Frederic Weisbecker <fweisbec@...il.com>,
Darren Hart <dvhart@...ux.intel.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"jason.wessel" <jason.wessel@...driver.com>,
Ted Ts'o <tytso@....edu>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Subject: Re: [RFC][PATCH 0/2] tracing: Have trace_printk()s in the events/
directory
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists