Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752197Ab3FYPaj (ORCPT ); Tue, 25 Jun 2013 11:30:39 -0400 Received: from one.firstfloor.org ([193.170.194.197]:33270 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751446Ab3FYPai (ORCPT ); Tue, 25 Jun 2013 11:30:38 -0400 Date: Tue, 25 Jun 2013 17:30:37 +0200 From: Andi Kleen To: "Yan, Zheng" Cc: linux-kernel@vger.kernel.org, mingo@kernel.org, a.p.zijlstra@chello.nl, eranian@google.com, andi@firstfloor.org Subject: Re: [PATCH 0/7] perf, x86: Haswell LBR call stack support Message-ID: <20130625153037.GA6123@two.firstfloor.org> References: <1372150039-15151-1-git-send-email-zheng.z.yan@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1372150039-15151-1-git-send-email-zheng.z.yan@intel.com> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1627 Lines: 42 On Tue, Jun 25, 2013 at 04:47:12PM +0800, Yan, Zheng wrote: > From: "Yan, Zheng" Can you put this description somewhere in Documentation as a file? (slightly extended, e.g. with the path name of the file to enable) I think the users will later need this kind of context to use the feature successfully. -Andi > > 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. When perf tool requests PERF_SAMPLE_CALLCHAIN + > PERF_SAMPLE_BRANCH_USER, this feature is dynamically enabled by default. > This feature can be disabled/enabled through an attribute file in the cpu > pmu sysfs directory. > > 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 > > These patches are based upon tip/perf/core > > Regards > Yan, Zheng > -- ak@linux.intel.com -- Speaking for myself only. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/