aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/builtin-script.c
diff options
context:
space:
mode:
authorAdrian Hunter <[email protected]>2014-08-12 15:04:31 +0000
committerArnaldo Carvalho de Melo <[email protected]>2014-08-13 19:24:13 +0000
commitf6edb53c4993ffe92ce521fb449d1c146cea6ec2 (patch)
tree49f920dcfeeb5e722d62da942d838bc6a0a2f06c /tools/perf/builtin-script.c
parentperf tools: Fix probing the kernel API with cpu-wide events (diff)
downloadkernel-f6edb53c4993ffe92ce521fb449d1c146cea6ec2.tar.gz
kernel-f6edb53c4993ffe92ce521fb449d1c146cea6ec2.zip
perf tools: Prefer to use a cpu-wide event for probing CLOEXEC
When doing a system-wide trace with Intel PT, the jump label set up as a result of probing CLOEXEC gets reset while the trace is running. That causes an Intel PT decoding error because the object code (obtained from /proc/kcore) does not match the running code at that point. While we can't expect there never to be jump label changes, we can avoid cases that the perf tool itself creates. The problem is avoided by first trying a cpu-wide event (pid = -1) for probing the PERF_FLAG_FD_CLOEXEC flag and falling back to an event for the current process (pid = 0). Signed-off-by: Adrian Hunter <[email protected]> Acked-by: Jiri Olsa <[email protected]> Cc: David Ahern <[email protected]> Cc: Frederic Weisbecker <[email protected]> Cc: Jiri Olsa <[email protected]> Cc: Namhyung Kim <[email protected]> Cc: Paul Mackerras <[email protected]> Cc: Peter Zijlstra <[email protected]> Cc: Stephane Eranian <[email protected]> Link: http://lkml.kernel.org/r/[email protected] Signed-off-by: Arnaldo Carvalho de Melo <[email protected]>
Diffstat (limited to 'tools/perf/builtin-script.c')
0 files changed, 0 insertions, 0 deletions