Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 2a3a4f66 authored by Frédéric Weisbecker's avatar Frédéric Weisbecker Committed by Ingo Molnar
Browse files

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: default avatarFrederic Weisbecker <fweisbec@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Steven Noonan <steven@uplinklabs.net>
Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
parent 35cb5ed0

kernel/trace/Kconfig

+5 −10
Original line number Diff line number Diff line 
#

# 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