From: Andi Kleen <[email protected]> According to Stephen there is no reason left not to allow function trace in perf code. Don't disable the function tracer instrumentation for the perf files. Changes the generic and the x86 files.
I've been using variants of this patch for a long time and haven't seen any problems. It's really useful to figure out why a complex perf_event_open() syscall fails. Cc: [email protected] Cc: [email protected] Signed-off-by: Andi Kleen <[email protected]> --- arch/x86/kernel/cpu/Makefile | 1 - kernel/events/Makefile | 4 ---- 2 files changed, 5 deletions(-) diff --git a/arch/x86/kernel/cpu/Makefile b/arch/x86/kernel/cpu/Makefile index 47b56a7..190bf4a 100644 --- a/arch/x86/kernel/cpu/Makefile +++ b/arch/x86/kernel/cpu/Makefile @@ -5,7 +5,6 @@ # Don't trace early stages of a secondary CPU boot ifdef CONFIG_FUNCTION_TRACER CFLAGS_REMOVE_common.o = -pg -CFLAGS_REMOVE_perf_event.o = -pg endif # Make sure load_percpu_segment has no stackprotector diff --git a/kernel/events/Makefile b/kernel/events/Makefile index 103f5d1..a630994 100644 --- a/kernel/events/Makefile +++ b/kernel/events/Makefile @@ -1,7 +1,3 @@ -ifdef CONFIG_FUNCTION_TRACER -CFLAGS_REMOVE_core.o = -pg -endif - obj-y := core.o ring_buffer.o callchain.o obj-$(CONFIG_HAVE_HW_BREAKPOINT) += hw_breakpoint.o -- 1.8.3.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
