Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751944Ab3EJJz3 (ORCPT ); Fri, 10 May 2013 05:55:29 -0400 Received: from 173-166-109-252-newengland.hfc.comcastbusiness.net ([173.166.109.252]:58178 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751152Ab3EJJz2 (ORCPT ); Fri, 10 May 2013 05:55:28 -0400 Date: Fri, 10 May 2013 11:53:45 +0200 From: Peter Zijlstra To: Jiri Olsa Cc: linux-kernel@vger.kernel.org, Corey Ashford , Frederic Weisbecker , Ingo Molnar , Namhyung Kim , Paul Mackerras , Arnaldo Carvalho de Melo , Andi Kleen , David Ahern , Stephane Eranian Subject: Re: [PATCH 0/9] perf: Adding better precise_ip field handling Message-ID: <20130510095345.GG3039@dyad.programming.kicks-ass.net> References: <1368106344-23383-1-git-send-email-jolsa@redhat.com> <20130509150744.GB3039@dyad.programming.kicks-ass.net> <20130509152022.GD1628@krava.brq.redhat.com> <20130510092741.GE3039@dyad.programming.kicks-ass.net> <20130510094053.GF1040@krava.brq.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130510094053.GF1040@krava.brq.redhat.com> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1319 Lines: 33 On Fri, May 10, 2013 at 11:40:53AM +0200, Jiri Olsa wrote: > nope, but I need a automated way to find out if PEBS > is supported in system Create an event, see what happens ;-) But I suppose you want to know if it should have worked vs does it actually work? Yeah, I suppose what you did is the right thing there. I was just completely missing the rationale earlier. > > > having maximum precise enabled with just single 'p' seemed > > > like good idea > > > > Doesn't seem like to me; that takes away the possibility to use less. > > hm, we could have another modifier to get system precise value > 'P' maybe.. and keep the 'p' logic That might be a possibility indeed. > > Also, you really don't need the max_precise for that either. At worst you'll > > have a number of unsuccessful event creations. > > so you mean just detect that by opening events with increasing > precise and see how far we could get.. could be I guess, though > the 'precise' sysfs attribute seems more fit to me The other way around, start at ppp end at !p, then use the one that worked. -- 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/