tracing/ftrace: separate events tracing and stats tracing engine
authorFrederic Weisbecker <fweisbec@gmail.com>
Sat, 10 Jan 2009 19:34:13 +0000 (11:34 -0800)
committerIngo Molnar <mingo@elte.hu>
Wed, 14 Jan 2009 11:11:37 +0000 (12:11 +0100)
commit002bb86d8d42f18937aef396c3ecd65c7e02e21a
treece8e81f6dc2515f6442198bbd4b527d900982f8e
parenta14a07b8018b714e03a39ff2180c66e307ef4238
tracing/ftrace: separate events tracing and stats tracing engine

Impact: tracing's Api change

Currently, the stat tracing depends on the events tracing.
When you switch to a new tracer, the stats files of the previous tracer
will disappear. But it's more scalable to separate those two engines.
This way, we can keep the stat files of one or several tracers when we
want, without bothering of multiple tracer stat files or tracer switching.

To build/destroys its stats files, a tracer just have to call
register_stat_tracer/unregister_stat_tracer everytimes it wants to.

Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
Signed-off-by: Steven Rostedt <srostedt@redhat.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
kernel/trace/trace.c
kernel/trace/trace.h
kernel/trace/trace_branch.c
kernel/trace/trace_stat.c
kernel/trace/trace_stat.h [new file with mode: 0644]