From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756689Ab3A0Mln (ORCPT ); Sun, 27 Jan 2013 07:41:43 -0500 Received: from mail-ea0-f176.google.com ([209.85.215.176]:58833 "EHLO mail-ea0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751247Ab3A0Mlj (ORCPT ); Sun, 27 Jan 2013 07:41:39 -0500 Date: Sun, 27 Jan 2013 13:41:33 +0100 From: Ingo Molnar To: Jiri Olsa Cc: linux-kernel@vger.kernel.org, Corey Ashford , Frederic Weisbecker , Ingo Molnar , Namhyung Kim , Paul Mackerras , Peter Zijlstra , Arnaldo Carvalho de Melo , Andi Kleen , David Ahern Subject: Re: [PATCH 0/9] perf: Adding better precise_ip field handling Message-ID: <20130127124133.GA3933@gmail.com> References: <1359221275-24254-1-git-send-email-jolsa@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1359221275-24254-1-git-send-email-jolsa@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Jiri Olsa wrote: > hi, > adding sysfs attribute to specify the maximum allowed value > for perf_event_attr::precise_ip field. > > Adding functionality for simple 'precise' term to get the > maximum allowed value for perf_event_attr::precise_ip field. > > And finally adding several precise automated tests. Ok - could we please as a next step turn on cycles:pp as the default in all the profiling tools (perf record, perf top), transparently? I.e. if the CPU supports it then use it, if not then don't complain, just use the highest grade profiling method available. Thanks, Ingo