[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1352183898-5601-1-git-send-email-zheng.z.yan@intel.com>
Date: Tue, 6 Nov 2012 14:38:11 +0800
From: "Yan, Zheng" <zheng.z.yan@...el.com>
To: linux-kernel@...r.kernel.org, a.p.zijlstra@...llo.nl
Cc: eranian@...gle.com, ak@...ux.intel.com,
"Yan, Zheng" <zheng.z.yan@...el.com>
Subject: [PATCH V3 0/7] perf, x86: Haswell LBR call stack support
From: "Yan, Zheng" <zheng.z.yan@...el.com>
Haswell has a new feature that utilizes the existing Last Branch Record
facility to record call chains. When the feature is enabled, function
call will be collected as normal, but as return instructions are executed
the last captured branch record is popped from the on-chip LBR registers.
The LBR call stack facility can help perf to get call chains of progam
without frame pointer.
The LBR call stack feature is automatic enabled when user requests sampling
user callchain. perf_callchain_user() outputs the hardware recorded call
stack in case there is no frame pointer in user program.
The LBR call stack has following known limitations
1. Zero length calls are not filtered out by hardware
2. Exception handing such as setjmp/longjmp will have calls/returns not
match
3. Pushing different return address onto the stack will have calls/returns
not match
The patch series depends on Andi's "perf PMU support for Haswel" patches
---
Changes since v1
- not expose PERF_SAMPLE_BRANCH_CALL_STACK to user space
- save/restore LBR stack on context switch for all sampling branch modes
- reduce lbr_sel_map size
Changes since v2
- only enable LBR call stack when user requests sampling user callchain
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists