From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754912Ab2JVGLZ (ORCPT ); Mon, 22 Oct 2012 02:11:25 -0400 Received: from mga01.intel.com ([192.55.52.88]:62982 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752589Ab2JVGLY (ORCPT ); Mon, 22 Oct 2012 02:11:24 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.80,628,1344236400"; d="scan'208";a="236689674" From: "Yan, Zheng" To: linux-kernel@vger.kernel.org, a.p.zijlstra@chello.nl Cc: eranian@google.com, ak@linux.intel.com, "Yan, Zheng" Subject: [PATCH 0/6] perf, x86: Haswell LBR call stack support Date: Mon, 22 Oct 2012 14:11:13 +0800 Message-Id: <1350886279-6141-1-git-send-email-zheng.z.yan@intel.com> X-Mailer: git-send-email 1.7.11.7 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: "Yan, Zheng" 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 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 Regards Yan, Zheng