From: Andi Kleen <andi@firstfloor.org>
To: Vince Weaver <vince@deater.net>
Cc: Andi Kleen <ak@linux.intel.com>, Andi Kleen <andi@firstfloor.org>,
acme@infradead.org, mingo@kernel.org,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>,
torvalds@linux-foundation.org, trinity@vger.kernel.org
Subject: Re: [PATCH 1/2] tools, perf: Add a precise event qualifier v2
Date: Wed, 24 Jul 2013 00:51:50 +0200 [thread overview]
Message-ID: <20130723225150.GT6123@two.firstfloor.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1307231717580.27628@pianoman.cluster.toy>
On Tue, Jul 23, 2013 at 05:27:43PM -0400, Vince Weaver wrote:
>
> I hate having to justify why breaking the ABI is unacceptable.
Well it's a testing ABI, so we can do changes to it.
I hope you're not suggesting that perf cannot be extended anymore.
As you know, hardware PMUs are constantly evolving, and perf has evolve
along with them to stay useful.
> It breaks the ABI. The events/* sysfs files are documented as only
> holding values for the bitfields described in format/*.
Ok. Need to fix the documentation then for precise=1. I'll send patches.
Also can add it to format/*, but since it's not in config* it will
be an extension. Since it would be awkward to teach every parser
about all the flags, we could add a "flags" field that is handled
like config, and contains all the flags.
So format/precise would be
flags:15-16
on little endian. Looks good?
> I'm a bit grumpy about this because I just finished fixing the fallout
> from your last time breaking the ABI a few weeks ago when your broken code
> started dumping non-hex fields into the sysfs event strings. I've learned
Not sure what you're talking about?
iirc the only recent sysfs change of mine merged recently was adding
intx/intx_cp, and format files never have had hex numbers in it.
> now that I have to go over your patches with a fine-tooth code because you
> have no regard for the ABI.
Any useful code review is appreciated.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2013-07-23 22:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1374501138-13496-1-git-send-email-andi@firstfloor.org>
[not found] ` <alpine.DEB.2.02.1307230137160.18617@pianoman.cluster.toy>
[not found] ` <20130723060108.GA18396@tassilo.jf.intel.com>
2013-07-23 21:27 ` [PATCH 1/2] tools, perf: Add a precise event qualifier v2 Vince Weaver
2013-07-23 22:51 ` Andi Kleen [this message]
2013-07-24 0:39 ` Sasha Levin
2013-07-24 1:33 ` Andi Kleen
2013-07-24 18:31 ` Vince Weaver
2013-07-24 18:54 ` Vince Weaver
2013-07-24 18:47 ` Vince Weaver
2013-07-24 19:05 ` Andi Kleen
2013-07-26 3:58 ` Vince Weaver
2013-09-12 16:57 ` Ingo Molnar
2013-09-12 17:36 ` Andi Kleen
2013-09-12 17:59 ` Ingo Molnar
2013-09-13 8:56 ` Peter Zijlstra
2013-09-13 9:50 ` Ingo Molnar
2013-09-13 11:29 ` Peter Zijlstra
2013-09-13 14:31 ` Vince Weaver
2013-09-13 17:48 ` Andi Kleen
2013-09-12 19:35 ` 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=20130723225150.GT6123@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=acme@infradead.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=trinity@vger.kernel.org \
--cc=vince@deater.net \
/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