perf/ftrace: Revert ("perf/ftrace: Fix double traces of perf on ftrace:function")
commit8fd0fbbe8888f295eb34172a7e47bf7d3a0a4687
authorPeter Zijlstra <peterz@infradead.org>
Wed, 11 Oct 2017 07:45:29 +0000 (11 09:45 +0200)
committerSteven Rostedt (VMware) <rostedt@goodmis.org>
Mon, 16 Oct 2017 22:11:02 +0000 (16 18:11 -0400)
tree86e13d1e79b9c407f4d142f12ea43fc1b008f617
parent136412474b77c14a26e018a7f2c1e5fcee700d3d
perf/ftrace: Revert ("perf/ftrace: Fix double traces of perf on ftrace:function")

Revert commit:

  75e8387685f6 ("perf/ftrace: Fix double traces of perf on ftrace:function")

The reason I instantly stumbled on that patch is that it only addresses the
ftrace situation and doesn't mention the other _5_ places that use this
interface. It doesn't explain why those don't have the problem and if not, why
their solution doesn't work for ftrace.

It doesn't, but this is just putting more duct tape on.

Link: http://lkml.kernel.org/r/20171011080224.200565770@infradead.org
Cc: Zhou Chengming <zhouchengming1@huawei.com>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
include/linux/perf_event.h
include/linux/trace_events.h
kernel/events/core.c
kernel/trace/trace_event_perf.c
kernel/trace/trace_kprobe.c
kernel/trace/trace_syscalls.c
kernel/trace/trace_uprobe.c