redonkable
/
alistair23-linux
1
0
Fork 0
Code Releases Activity

tracing/ftrace: tracing engine depends on Nop Tracer 

Now that the nop tracer is used as the default tracer by
replacing the "none" tracer, tracing engine depends on it.

Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Steven Noonan <steven@uplinklabs.net>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
hifive-unleashed-5.1
Frédéric Weisbecker 2008-09-21 20:12:14 +02:00 committed by Ingo Molnar
parent 35cb5ed012
commit 2a3a4f669d
1 changed files with 5 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
kernel/trace/Kconfig
View File

@ -1,8 +1,13 @@
#
# Architectures that offer an FTRACE implementation should select HAVE_FTRACE:
#
config NOP_TRACER
bool
config HAVE_FTRACE
bool
select NOP_TRACER
config HAVE_DYNAMIC_FTRACE
bool
@ -101,16 +106,6 @@ config SCHED_TRACER
This tracer tracks the latency of the highest priority task
to be scheduled in, starting from the point it has woken up.
config NOP_TRACER
bool "NOP Tracer"
depends on HAVE_FTRACE
depends on DEBUG_KERNEL
select TRACING
help
This tracer does nothing. The primary purpose for it is to
politely print the output of ftrace_printk() calls without
the overhead of an irrelevant trace taking place.
config CONTEXT_SWITCH_TRACER
bool "Trace process context switches"
depends on HAVE_FTRACE