Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752209AbaBZQDf (ORCPT ); Wed, 26 Feb 2014 11:03:35 -0500 Received: from mail-vc0-f178.google.com ([209.85.220.178]:42335 "EHLO mail-vc0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752038AbaBZQDe (ORCPT ); Wed, 26 Feb 2014 11:03:34 -0500 MIME-Version: 1.0 In-Reply-To: References: <1392703661-15104-1-git-send-email-zheng.z.yan@intel.com> <530D53EF.9090706@amacapital.net> From: Andy Lutomirski Date: Wed, 26 Feb 2014 09:03:13 -0700 Message-ID: Subject: Re: [PATCH v3 00/14] perf, x86: Haswell LBR call stack support To: Stephane Eranian Cc: "Yan, Zheng" , LKML , Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Andi Kleen Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 26, 2014 at 12:04 AM, Stephane Eranian wrote: > On Wed, Feb 26, 2014 at 3:39 AM, Andy Lutomirski wrote: >> On 02/17/2014 10:07 PM, Yan, Zheng wrote: >>> >>> This patch series adds LBR call stack support. User can enabled/disable >>> this through an sysfs attribute file in the CPU PMU directory: >>> echo 1 > /sys/bus/event_source/devices/cpu/lbr_callstack >> >> This seems like an unpleasant way to control this. It would be handy to >> be able to control this as an option to perf record. >> > That would mean you'd be root for perf. > Or are you suggesting a perf event option? But then, you'd expose arch-specific > feature at the API level. > I'm suggesting a perf event option, just like the way that PEBS works. --Andy -- 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/