Commit f3384b28 authored by Steven Rostedt's avatar Steven Rostedt Committed by Ingo Molnar

ftrace: fix trace_nop config select

Impact: build fix on non-function-tracing architectures

The trace_nop is the tracer that is defined when no tracer is set in
the ftrace infrastructure.

The trace_nop was mistakenly selected by HAVE_FTRACE due to the confusion
between ftrace infrastructure and the ftrace function tracer (which has
been solved by renaming the function tracer).

This patch changes the select to the approriate TRACING.

This patch should fix compile errors on architectures that do not define
the FUNCTION_TRACER.
Signed-off-by: default avatarSteven Rostedt <srostedt@redhat.com>
Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
parent 0b6e4d56
...@@ -8,7 +8,6 @@ config NOP_TRACER ...@@ -8,7 +8,6 @@ config NOP_TRACER
config HAVE_FUNCTION_TRACER config HAVE_FUNCTION_TRACER
bool bool
select NOP_TRACER
config HAVE_DYNAMIC_FTRACE config HAVE_DYNAMIC_FTRACE
bool bool
...@@ -28,6 +27,7 @@ config TRACING ...@@ -28,6 +27,7 @@ config TRACING
select RING_BUFFER select RING_BUFFER
select STACKTRACE select STACKTRACE
select TRACEPOINTS select TRACEPOINTS
select NOP_TRACER
menu "Tracers" menu "Tracers"
......
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