Hi Dmitry,
On Fri, Feb 24, 2012 at 4:23 PM, Dmitry Antipov dmitry.antipov@linaro.org wrote:
On 02/23/2012 04:57 AM, Ming Lei wrote:
No, it doesn't work with upstream kernel now. You need to apply the patches[1][2] against upstream kernel to route CTIs IRQ so that OMAP4 PMU/perf can work well.
[1], http://marc.info/?l=linux-omap&m=132686049213313&w=2 [2], http://marc.info/?l=linux-arm-kernel&m=132687938417894&w=2
I'm not sure about "well" :-(:
... irq 34: nobody cared (try booting with the "irqpoll" option) ... Disabling IRQ #34 irq 33: nobody cared (try booting with the "irqpoll" option) ... Disabling IRQ #33
Could you try the patch below to see if it can fix your oprofile problem?
In fact, I observed this patch can fix the same problem triggered by the command below:
# frequency should be set as more than 40000 perf record -e cycles -F 50000 noploop
diff --git a/arch/arm/mach-omap2/devices.c b/arch/arm/mach-omap2/devices.c index d055abc..9c12bfa 100644 --- a/arch/arm/mach-omap2/devices.c +++ b/arch/arm/mach-omap2/devices.c @@ -507,7 +507,7 @@ static void __init omap4_configure_pmu_irq(void) /*configure CTI1 for pmu irq routing*/ cti_init(&omap4_cti[1], base1, OMAP44XX_IRQ_CTI1, 6); cti_unlock(&omap4_cti[1]); - cti_map_trigger(&omap4_cti[1], 1, 6, 2); + cti_map_trigger(&omap4_cti[1], 1, 6, 3); }
static struct platform_device* __init omap4_init_pmu(void)
Thanks, -- Ming Lei