aboutsummaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authorSteven Rostedt <srostedt@redhat.com>2010-06-10 14:53:16 -0400
committerSteven Rostedt <rostedt@goodmis.org>2010-06-10 20:56:54 -0400
commita8fb2608053547bc3152ea61a5ec7cdfce5d942c (patch)
tree08f5fd61dd3fce05a2472f457c48ec249966b372 /tools
parentd11007703c31db534674ebeeb9eb047bbbe758bd (diff)
downloadmrst-s0i3-test-a8fb2608053547bc3152ea61a5ec7cdfce5d942c.tar.gz
mrst-s0i3-test-a8fb2608053547bc3152ea61a5ec7cdfce5d942c.tar.xz
mrst-s0i3-test-a8fb2608053547bc3152ea61a5ec7cdfce5d942c.zip
perf/tracing: Fix regression of perf losing kprobe events
With the addition of the code to shrink the kernel tracepoint infrastructure, we lost kprobes being traced by perf. The reason is that I tested if the "tp_event->class->perf_probe" existed before enabling it. This prevents "ftrace only" events (like the function trace events) from being enabled by perf. Unfortunately, kprobe events do not use perf_probe. This causes kprobes to be missed by perf. To fix this, we add the test to see if "tp_event->class->reg" exists as well as perf_probe. Normal trace events have only "perf_probe" but no "reg" function, and kprobes and syscalls have the "reg" but no "perf_probe". The ftrace unique events do not have either, so this is a valid test. If a kprobe or syscall is not to be probed by perf, the "reg" function is called anyway, and will return a failure and prevent perf from probing it. Reported-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com> Tested-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com> Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions