From: Peter Zijlstra <peterz@infradead.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: perf: more ABI breakage
Date: Mon, 8 Jul 2013 18:47:21 +0200 [thread overview]
Message-ID: <20130708164721.GC22923@dyad.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1307081115350.2281@vincent-weaver-1.um.maine.edu>
On Mon, Jul 08, 2013 at 11:24:18AM -0400, Vince Weaver wrote:
>
> I guess I should have been noisier about this at the time.
>
> Linux 3.9 came with commit
> e259514eef764a5286873618e34c560ecb6cff13
> that enabled AMD fam15h Northbridge support, by exposing the events as
> part of the core CPU.
>
> Then Linux 3.10 changed this with
> c43ca5091a374c1f6778bd7e4a39a5a10735a917
> and split them out as a separate PMU.
>
> This of course breaks libpfm4 and thus PAPI
Urgh, so the 3.9 patches should never have been merged and sunk in while I was
doing my vegetable imitation.
Stephane agreed with the change in 3.10; and I suppose he overlooked the fact
that people were already using it :/ I specifically asked if there were already
users as that would indeed require some form of backwards compatibility --
however annoying.
But to answer your question, no we should not blindly break stuff like this --
but yeah it would have been ever so much more useful for people to report this
before we ship a release.
Stephane; do you see a sane way to bridge this now?
next prev parent reply other threads:[~2013-07-08 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 15:24 perf: more ABI breakage Vince Weaver
2013-07-08 16:47 ` Peter Zijlstra [this message]
2013-07-08 19:08 ` Vince Weaver
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=20130708164721.GC22923@dyad.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.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