Commit 5f87f112 authored by Ingo Molnar's avatar Ingo Molnar

tracing: clean up tracepoints kconfig structure

do not expose users to CONFIG_TRACEPOINTS - tracers can select it
just fine.

update ftrace to select CONFIG_TRACEPOINTS.
Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
parent cf569a93
...@@ -771,11 +771,12 @@ config PROFILING ...@@ -771,11 +771,12 @@ config PROFILING
Say Y here to enable the extended profiling support mechanisms used Say Y here to enable the extended profiling support mechanisms used
by profilers such as OProfile. by profilers such as OProfile.
#
# Place an empty function call at each tracepoint site. Can be
# dynamically changed for a probe function.
#
config TRACEPOINTS config TRACEPOINTS
bool "Activate tracepoints" bool
help
Place an empty function call at each tracepoint site. Can be
dynamically changed for a probe function.
config MARKERS config MARKERS
bool "Activate markers" bool "Activate markers"
......
...@@ -14,6 +14,7 @@ config TRACING ...@@ -14,6 +14,7 @@ config TRACING
bool bool
select DEBUG_FS select DEBUG_FS
select STACKTRACE select STACKTRACE
select TRACEPOINTS
config FTRACE config FTRACE
bool "Kernel Function Tracer" bool "Kernel Function Tracer"
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment