tracing/ftrace: separate events tracing and stats tracing engine

Browse source

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>

...

This commit is contained in:

Frederic Weisbecker 2009-01-10 11:34:13 -08:00 • committed by Ingo Molnar

parent a14a07b801

commit 002bb86d8d

5 changed files with 172 additions and 180 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

kernel/trace/trace.c

View file

20

kernel/trace/trace.h

View file

108

kernel/trace/trace_branch.c

View file

193

kernel/trace/trace_stat.c

View file

31

kernel/trace/trace_stat.h

View file