From: "Frédéric Weisbecker" <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Steven Noonan <steven@uplinklabs.net>
Subject: [Patch 2/3] Tracing/ftrace: Tracing engine depends on Nop Tracer
Date: Sun, 21 Sep 2008 20:12:14 +0200 [thread overview]
Message-ID: <48D68E7E.4010902@gmail.com> (raw)
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
reply other threads:[~2008-09-21 18:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48D68E7E.4010902@gmail.com \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=steven@uplinklabs.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox