From: Michael Ellerman <michael@ellerman.id.au>
To: acme@infradead.org
Cc: peterz@infradead.org, jolsa@redhat.com,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
rob@landley.net
Subject: Re: [RFC/PATCH] perf: Expand definition of sysfs format attribute
Date: Mon, 6 May 2013 11:08:30 +1000 [thread overview]
Message-ID: <20130506010829.GA32607@concordia> (raw)
In-Reply-To: <20130408072422.GA4476@concordia>
On Mon, Apr 08, 2013 at 05:24:22PM +1000, Michael Ellerman wrote:
> On Mon, Mar 04, 2013 at 03:21:05PM +1100, Michael Ellerman wrote:
> > Make it explicit that the format attributes may define overlapping bit
> > ranges. Unfortunately this was left unspecified originally, and all the
> > examples show non-overlapping ranges. I don't believe this is an ABI
> > change, as we are defining something that was previously undefined, but
> > others may disagree.
> >
> > The POWER8 PMU would like to define overlapping ranges, as bit ranges in
> > the event code have different meanings for certain events. It will also
> > allow us to define an overarching "event" field, that encompasses all
> > others.
> >
> > As far as I can see perf is comfortable with this change, however I am
> > not sure if there are any other users of the interface.
>
> Any comments on this one?
Hi Arnaldo,
I think the consensus from Peter and Jiri was that this was OK, are you
happy to merge it?
cheers
next prev parent reply other threads:[~2013-05-06 1:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 4:21 [RFC/PATCH] perf: Expand definition of sysfs format attribute Michael Ellerman
2013-04-08 7:24 ` Michael Ellerman
2013-05-06 1:08 ` Michael Ellerman [this message]
2013-05-06 8:20 ` Arnaldo Carvalho de Melo
2013-05-06 11:36 ` Jiri Olsa
2013-04-08 9:05 ` Peter Zijlstra
2013-04-08 11:57 ` Michael Ellerman
2013-04-08 15:51 ` Jiri Olsa
2013-05-10 15:27 ` Peter Zijlstra
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=20130506010829.GA32607@concordia \
--to=michael@ellerman.id.au \
--cc=acme@infradead.org \
--cc=jolsa@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rob@landley.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