diff options
author | Peter Zijlstra <a.p.zijlstra@chello.nl> | 2010-03-03 13:12:23 +0100 |
---|---|---|
committer | Ingo Molnar <mingo@elte.hu> | 2010-03-10 13:23:32 +0100 |
commit | ef21f683a045a79b6aa86ad81e5fdfc0d5ddd250 (patch) | |
tree | ccf39f5051608c1eccac9171259c2d7bc381cc96 /arch/x86/include/asm/ioctls.h | |
parent | caff2befffe899e63df5cc760b7ed01cfd902685 (diff) | |
download | talos-op-linux-ef21f683a045a79b6aa86ad81e5fdfc0d5ddd250.tar.gz talos-op-linux-ef21f683a045a79b6aa86ad81e5fdfc0d5ddd250.zip |
perf, x86: use LBR for PEBS IP+1 fixup
Use the LBR to fix up the PEBS IP+1 issue.
As said, PEBS reports the next instruction, here we use the LBR to find
the last branch and from that construct the actual IP. If the IP matches
the LBR-TO, we use LBR-FROM, otherwise we use the LBR-TO address as the
beginning of the last basic block and decode forward.
Once we find a match to the current IP, we use the previous location.
This patch introduces a new ABI element: PERF_RECORD_MISC_EXACT, which
conveys that the reported IP (PERF_SAMPLE_IP) is the exact instruction
that caused the event (barring CPU errata).
The fixup can fail due to various reasons:
1) LBR contains invalid data (quite possible)
2) part of the basic block got paged out
3) the reported IP isn't part of the basic block (see 1)
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: Masami Hiramatsu <mhiramat@redhat.com>
Cc: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: paulus@samba.org
Cc: eranian@google.com
Cc: robert.richter@amd.com
Cc: fweisbec@gmail.com
LKML-Reference: <20100304140100.619375431@chello.nl>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'arch/x86/include/asm/ioctls.h')
0 files changed, 0 insertions, 0 deletions