From mboxrd@z Thu Jan  1 00:00:00 1970
From: Will Deacon <will.deacon@arm.com>
Subject: Re: oprofile and ARM A9 hardware counter
Date: Fri, 11 May 2012 14:49:21 +0100
Message-ID: <20120511134920.GC2626@mudshark.cambridge.arm.com>
References: <4FA9588E.9020906@ti.com>
 <87sjfal65t.fsf@ti.com>
 <4FAA4DB9.8060504@ti.com>
 <4FAAB1A3.9040806@ti.com>
 <4FAAC549.6010206@ti.com>
 <4FAAE564.6040708@ti.com>
 <20120510084422.GB27276@mudshark.cambridge.arm.com>
 <4FAC0F05.3060803@ti.com>
 <20120511122547.GE17453@mudshark.cambridge.arm.com>
 <4FAD1865.70003@ti.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <linux-omap-owner@vger.kernel.org>
Received: from cam-admin0.cambridge.arm.com ([217.140.96.50]:40702 "EHLO
	cam-admin0.cambridge.arm.com" rhost-flags-OK-OK-OK-OK)
	by vger.kernel.org with ESMTP id S1751647Ab2EKNtt (ORCPT
	<rfc822;linux-omap@vger.kernel.org>);
	Fri, 11 May 2012 09:49:49 -0400
Content-Disposition: inline
In-Reply-To: <4FAD1865.70003@ti.com>
Sender: linux-omap-owner@vger.kernel.org
List-Id: linux-omap@vger.kernel.org
To: Jon Hunter <jon-hunter@ti.com>
Cc: "Cousson, Benoit" <b-cousson@ti.com>, Kevin Hilman <khilman@ti.com>, Paul Walmsley <paul@pwsan.com>, Ming Lei <ming.lei@canonical.com>, Maynard Johnson <maynardj@us.ibm.com>, "Shilimkar, Santosh" <santosh.shilimkar@ti.com>, "oprofile-list@lists.sourceforge.net" <oprofile-list@lists.sourceforge.net>, Lik Lik <lik88888@gmail.com>, "eranian@gmail.com" <eranian@gmail.com>, "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>

On Fri, May 11, 2012 at 02:47:17PM +0100, Jon Hunter wrote:
> On 05/11/2012 07:25 AM, Will Deacon wrote:
> > I figured I may as well take perf for a spin and see how I got on. The good
> > news is that the hwmod bits all seem to work as before and the correct IRQs
> > are requested:
> > 
> > root@florentine-pogen:~# cat /proc/interrupts
> >            CPU0       CPU1
> >  29:      44527      17916       GIC  twd
> >  33:          0          0       GIC  arm-pmu
> >  34:          0          0       GIC  arm-pmu
> > 
> > But, unfortunately, as you can see from the above, I just can't persuade them
> > to fire. The PMU counters do tick, but they happily increment through zero
> > without us realising. I retested with my perf/omap4 branch to make sure my
> > board is ok, and the irqs do fire there.
> > 
> > Any ideas?
> 
> Do you disable OMAP2/3 support in the kernel config, so that CPU_HAS_PMU
> is enabled?

I enabled OMAP3 debug peripherals, so I selected CPU_HAS_PMU that way.

Will