Commit 4d7a077c authored by Steven Rostedt's avatar Steven Rostedt
Browse files

tracing: have function trace select kallsyms 



Impact: fix output of function tracer to be useful

The function tracer is pretty useless if KALLSYMS is not configured.
Unless you are good at reading hex values, the function tracer should
select the KALLSYMS configuration.

Also, the dynamic function tracer will fail its self test if KALLSYMS
is not selected.

Signed-off-by: default avatarSteven Rostedt <srostedt@redhat.com>
parent 0c5119c1

kernel/trace/Kconfig

+2 −0
Original line number Diff line number Diff line
@@ -52,6 +52,7 @@ config FUNCTION_TRACER 
	depends on HAVE_FUNCTION_TRACER

	depends on DEBUG_KERNEL

	select FRAME_POINTER

	select KALLSYMS

	select TRACING

	select CONTEXT_SWITCH_TRACER

	help
@@ -238,6 +239,7 @@ config STACK_TRACER 
	depends on DEBUG_KERNEL

	select FUNCTION_TRACER

	select STACKTRACE

	select KALLSYMS

	help

	  This special tracer records the maximum stack footprint of the

	  kernel and displays it in debugfs/tracing/stack_trace.

CRA Git | Maintained and supported by SUSTech CRA and CCSE