[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131030232148.GC27743@mudshark.cambridge.arm.com>
Date: Wed, 30 Oct 2013 23:21:49 +0000
From: Will Deacon <will.deacon@....com>
To: Vince Weaver <vincent.weaver@...ne.edu>
Cc: Peter Zijlstra <peterz@...radead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
"eranian@...gle.com" <eranian@...gle.com>
Subject: Re: perf: PERF_EVENT_IOC_PERIOD on ARM vs everywhere else
On Wed, Oct 30, 2013 at 02:13:11PM +0000, Vince Weaver wrote:
> On Wed, 30 Oct 2013, Peter Zijlstra wrote:
> > The below code should deal with both cases I think -- completely
> > untested.
>
> Uncompiled too I guess?
>
> kernel/events/core.c: In function ‘perf_event_period’:
> kernel/events/core.c:3531: error: invalid type argument of ‘->’ (have ‘local64_t’)
> make[3]: *** [kernel/events/core.o] Error 1
That's trivial to fix.
> I also won't be able to test the ARM change, as my pandaboard won't boot
> with recent kernels (can't find the MMC root filesystem) and I haven't had
> time to track down why. Also even on a simple period changing test it
> often fails due to lost interrupts (the Cortex-A9 lost interrupt errata?).
The omap guys like trying to blame the A9 erratum for that (which doesn't
even affect the cycle counter), but the reality is that the CTI never
worked reliably with mainline, and now there are no developers working
on that after the TI layoffs. I don't see the state of Pandaboard support
improving over time.
If you have a canned testcase for this stuff, I'm happy to run it on my
Chromebook.
Will
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists