Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753341AbaAJJl0 (ORCPT ); Fri, 10 Jan 2014 04:41:26 -0500 Received: from merlin.infradead.org ([205.233.59.134]:55012 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751919AbaAJJlW (ORCPT ); Fri, 10 Jan 2014 04:41:22 -0500 Date: Fri, 10 Jan 2014 10:40:56 +0100 From: Peter Zijlstra To: Vince Weaver Cc: Will Deacon , Chad Paradis , "linux-kernel@vger.kernel.org" , Paul Mackerras , Ingo Molnar , Arnaldo Carvalho de Melo , Stephane Eranian Subject: Re: [patch/rfc] perf on raspberry-pi without overflow interrupt Message-ID: <20140110094056.GK31570@twins.programming.kicks-ass.net> References: <20140108225315.GG31570@twins.programming.kicks-ass.net> <20140109101921.GA26435@mudshark.cambridge.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 On Thu, Jan 09, 2014 at 11:08:47PM -0500, Vince Weaver wrote: > On Thu, 9 Jan 2014, Will Deacon wrote: > > > I'd rather see it in the generic code if at all possible. Maybe we could add > > a flags field to perf_pmu_register? > > I can look into adding the check in generic code. Adding something like this to the generic code would mean adding a struct pmu capabilities field and visiting all existing PMU implementations to properly fill this out. There's a number of hardware PMU implementations that do not have an interrupt and would need to set this flag. -- 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/