From: Will Deacon <will.deacon@arm.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: Peter Zijlstra <peterz@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
"eranian@google.com" <eranian@google.com>
Subject: Re: perf: PERF_EVENT_IOC_PERIOD on ARM vs everywhere else
Date: Wed, 30 Oct 2013 23:21:49 +0000 [thread overview]
Message-ID: <20131030232148.GC27743@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1310301006190.8668@vincent-weaver-1.um.maine.edu>
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
next prev parent reply other threads:[~2013-10-30 23:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 2:37 perf: PERF_EVENT_IOC_PERIOD on ARM vs everywhere else Vince Weaver
2013-10-28 8:57 ` Will Deacon
2013-10-28 10:00 ` Peter Zijlstra
2013-10-28 12:53 ` Will Deacon
2013-10-28 14:07 ` Vince Weaver
2013-10-29 4:28 ` Will Deacon
2013-10-29 13:45 ` Peter Zijlstra
2013-10-29 15:36 ` Vince Weaver
2013-10-30 9:56 ` Peter Zijlstra
2013-10-30 11:01 ` Stephane Eranian
2013-10-30 14:13 ` Vince Weaver
2013-10-30 23:21 ` Will Deacon [this message]
2013-10-31 15:25 ` Vince Weaver
2013-11-05 13:34 ` Will Deacon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131030232148.GC27743@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=acme@ghostprotocols.net \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vincent.weaver@maine.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox