linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Yan, Zheng" <zheng.z.yan@intel.com>
To: linux-kernel@vger.kernel.org, a.p.zijlstra@chello.nl
Cc: eranian@google.com, ak@linux.intel.com, "Yan,
	Zheng" <zheng.z.yan@intel.com>
Subject: [PATCH V3 0/7] perf, x86: Haswell LBR call stack support
Date: Tue,  6 Nov 2012 14:38:11 +0800	[thread overview]
Message-ID: <1352183898-5601-1-git-send-email-zheng.z.yan@intel.com> (raw)

From: "Yan, Zheng" <zheng.z.yan@intel.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

             reply	other threads:[~2012-11-06  6:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-06  6:38 Yan, Zheng [this message]
2012-11-06  6:38 ` [PATCH V3 1/7] perf, x86: Reduce lbr_sel_map size Yan, Zheng
2012-11-06  6:38 ` [PATCH V3 2/7] perf, x86: Basic Haswell LBR call stack support Yan, Zheng
2012-11-06  6:38 ` [PATCH V3 3/7] perf, x86: Introduce x86 special perf event context Yan, Zheng
2012-11-06  6:38 ` [PATCH V3 4/7] perf, x86: Save/resotre LBR stack during context switch Yan, Zheng
2012-11-06  6:38 ` [PATCH V3 5/7] perf, core: Pass perf_sample_data to perf_callchain() Yan, Zheng
2012-11-06  6:38 ` [PATCH V3 6/7] perf, x86: Use LBR call stack to get user callchain Yan, Zheng
2012-11-06  6:38 ` [PATCH V3 7/7] perf, x86: Discard zero length call entries in LBR call stack Yan, Zheng
  -- strict thread matches above, loose matches on Subject: below --
2013-02-25  2:01 [PATCH V3 0/7] perf, x86: Haswell LBR call stack support 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=1352183898-5601-1-git-send-email-zheng.z.yan@intel.com \
    --to=zheng.z.yan@intel.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=ak@linux.intel.com \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).