From: Will Deacon <will.deacon@arm.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: perf: PERF_EVENT_IOC_PERIOD on ARM vs everywhere else
Date: Tue, 29 Oct 2013 04:28:10 +0000 [thread overview]
Message-ID: <20131029042810.GD22291@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1310281002020.24060@vincent-weaver-1.um.maine.edu>
On Mon, Oct 28, 2013 at 02:07:48PM +0000, Vince Weaver wrote:
> It's also a shame this change apprently didn't hit the linux-kernel list
> as far as I can tell. I do my best to try to note all of the perf
> ABI-related changes there, but if things like this are going to start
> getting merged in architecture trees then things get that much harder
> to keep track of.
I can CC LKML on ARM perf patches if you think it will help, but all PMU
backend patches go via their respective arch trees afaict.
> > I don't want to be the `oddball' architecture (at least, not more than I am
> > already :), but I do find it tricky to follow the required semantics of perf
> > as opposed to `it happens to work this way', especially when so much of it
> > is buried in the various arch backends. So if somebody using the thing on
> > ARM has (what looks to me like) a valid issue, then I usually try and fix
> > it.
>
> But it was global behavior that was common on all architectures.
>
> Now any cross-platform tool like PAPI is going to have to have a mess of
> #ifdefs around every use of this ioctl, and it will only get worse if
> other architectures decide to "fix" the problem too.
What would you like me to do to fix this for you? Moving more code out of
the backends and into the core will help maintain consistency between
architectures, but that's a huge job.
Will
next prev parent reply other threads:[~2013-10-29 4:29 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 [this message]
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
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=20131029042810.GD22291@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=acme@ghostprotocols.net \
--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