From: "Yan, Zheng" <zheng.z.yan@intel.com>
To: linux-kernel@vger.kernel.org
Cc: a.p.zijlstra@chello.nl, mingo@kernel.org, acme@infradead.org,
eranian@google.com, andi@firstfloor.org, "Yan,
Zheng" <zheng.z.yan@intel.com>
Subject: [PATCH v4 16/16] perf, x86: Discard zero length call entries in LBR call stack
Date: Mon, 17 Mar 2014 13:57:36 +0800 [thread overview]
Message-ID: <1395035856-15411-17-git-send-email-zheng.z.yan@intel.com> (raw)
In-Reply-To: <1395035856-15411-1-git-send-email-zheng.z.yan@intel.com>
"Zero length call" uses the attribute of the call instruction to push
the immediate instruction pointer on to the stack and then pops off
that address into a register. This is accomplished without any matching
return instruction. It confuses the hardware and make the recorded call
stack incorrect.
We can partially resolve this issue by: decode call instructions and
discard any zero length call entry in the LBR stack.
Signed-off-by: Yan, Zheng <zheng.z.yan@intel.com>
---
arch/x86/kernel/cpu/perf_event_intel_lbr.c | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/cpu/perf_event_intel_lbr.c b/arch/x86/kernel/cpu/perf_event_intel_lbr.c
index 5a6ea1c..10bcda6 100644
--- a/arch/x86/kernel/cpu/perf_event_intel_lbr.c
+++ b/arch/x86/kernel/cpu/perf_event_intel_lbr.c
@@ -94,7 +94,8 @@ enum {
X86_BR_ABORT = 1 << 12,/* transaction abort */
X86_BR_IN_TX = 1 << 13,/* in transaction */
X86_BR_NO_TX = 1 << 14,/* not in transaction */
- X86_BR_CALL_STACK = 1 << 15,/* call stack */
+ X86_BR_ZERO_CALL = 1 << 15,/* zero length call */
+ X86_BR_CALL_STACK = 1 << 16,/* call stack */
};
#define X86_BR_PLM (X86_BR_USER | X86_BR_KERNEL)
@@ -111,13 +112,15 @@ enum {
X86_BR_JMP |\
X86_BR_IRQ |\
X86_BR_ABORT |\
- X86_BR_IND_CALL)
+ X86_BR_IND_CALL |\
+ X86_BR_ZERO_CALL)
#define X86_BR_ALL (X86_BR_PLM | X86_BR_ANY)
#define X86_BR_ANY_CALL \
(X86_BR_CALL |\
X86_BR_IND_CALL |\
+ X86_BR_ZERO_CALL |\
X86_BR_SYSCALL |\
X86_BR_IRQ |\
X86_BR_INT)
@@ -659,6 +662,12 @@ static int branch_type(unsigned long from, unsigned long to, int abort)
ret = X86_BR_INT;
break;
case 0xe8: /* call near rel */
+ insn_get_immediate(&insn);
+ if (insn.immediate1.value == 0) {
+ /* zero length call */
+ ret = X86_BR_ZERO_CALL;
+ break;
+ }
case 0x9a: /* call far absolute */
ret = X86_BR_CALL;
break;
--
1.8.5.3
next prev parent reply other threads:[~2014-03-17 5:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 5:57 [PATCH v4 00/16] perf, x86: Haswell LBR call stack support Yan, Zheng
2014-03-17 5:57 ` [PATCH v4 01/16] perf, x86: Reduce lbr_sel_map size Yan, Zheng
2014-03-17 5:57 ` [PATCH v4 02/16] perf, core: introduce pmu context switch callback Yan, Zheng
2014-03-17 5:57 ` [PATCH v4 03/16] perf, x86: use context switch callback to flush LBR stack Yan, Zheng
2014-03-17 5:57 ` [PATCH v4 04/16] perf, x86: Basic Haswell LBR call stack support Yan, Zheng
2014-03-17 5:57 ` [PATCH v4 05/16] perf, core: pmu specific data for perf task context Yan, Zheng
2014-03-17 5:57 ` [PATCH v4 06/16] perf, core: always switch pmu specific data during context switch Yan, Zheng
2014-03-17 5:57 ` [PATCH v4 07/16] perf, x86: track number of events that use LBR callstack Yan, Zheng
2014-03-17 5:57 ` [PATCH v4 08/16] perf, x86: allocate space for storing LBR stack Yan, Zheng
2014-03-17 5:57 ` [PATCH v4 09/16] perf, x86: Save/resotre LBR stack during context switch Yan, Zheng
2014-03-17 5:57 ` [PATCH v4 10/16] perf, core: simplify need branch stack check Yan, Zheng
2014-03-17 5:57 ` [PATCH v4 11/16] perf, core: Pass perf_sample_data to perf_callchain() Yan, Zheng
2014-03-17 5:57 ` [PATCH v4 12/16] perf, x86: use LBR call stack to get user callchain Yan, Zheng
2014-03-17 5:57 ` [PATCH v4 13/16] perf, x86: re-organize code that implicitly enables LBR/PEBS Yan, Zheng
2014-03-17 5:57 ` [PATCH v4 14/16] perf, x86: enable LBR callstack when recording callchain Yan, Zheng
2014-03-17 5:57 ` [PATCH v4 15/16] perf, x86: disable FREEZE_LBRS_ON_PMI when LBR operates in callstack mode Yan, Zheng
2014-03-17 5:57 ` Yan, Zheng [this message]
2014-06-30 8:50 [PATCH V4 00/16] perf, x86: Haswell LBR call stack support Yan, Zheng
2014-06-30 8:50 ` [PATCH V4 16/16] perf, x86: Discard zero length call entries in LBR call stack Yan, Zheng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1395035856-15411-17-git-send-email-zheng.z.yan@intel.com \
--to=zheng.z.yan@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®