* [Patch 2/3] Tracing/ftrace: Tracing engine depends on Nop Tracer
@ 2008-09-21 18:12 Frédéric Weisbecker
0 siblings, 0 replies; only message in thread
From: Frédéric Weisbecker @ 2008-09-21 18:12 UTC (permalink / raw)
To: Ingo Molnar; +Cc: Linux Kernel, Steven Rostedt, Steven Noonan
Now that nop tracer is used as the default tracer by replacing "none" tracer, tracing engine depends on it.
Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
---
diff -rup linux-2.6-tip (2)/kernel/trace/Kconfig linux-2.6-tip/kernel/trace/Kconfig
--- linux-2.6-tip (2)/kernel/trace/Kconfig 2008-09-19 18:01:26.000000000 +0200
+++ linux-2.6-tip/kernel/trace/Kconfig 2008-09-21 00:31:48.000000000 +0200
@@ -1,8 +1,13 @@
#
# Architectures that offer an FTRACE implementation should select HAVE_FTRACE:
-#
+#
+
+config NOP_TRACER
+ bool
+
config HAVE_FTRACE
- bool
+ 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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2008-09-21 18:12 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-09-21 18:12 [Patch 2/3] Tracing/ftrace: Tracing engine depends on Nop Tracer Frédéric Weisbecker
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox