From: Peter Zijlstra <peterz@infradead.org>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: acme@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: Fri, 10 May 2013 17:27:38 +0200 [thread overview]
Message-ID: <20130510152738.GA885@dyad.programming.kicks-ass.net> (raw)
In-Reply-To: <1362370865-4437-1-git-send-email-michael@ellerman.id.au>
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.
>
> Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
Jiri was going to collect to send to Ingo..
Acked-by: Peter Zijlstra <peterz@infradead.org>
> ---
> Documentation/ABI/testing/sysfs-bus-event_source-devices-format | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/ABI/testing/sysfs-bus-event_source-devices-format b/Documentation/ABI/testing/sysfs-bus-event_source-devices-format
> index 079afc7..77f47ff 100644
> --- a/Documentation/ABI/testing/sysfs-bus-event_source-devices-format
> +++ b/Documentation/ABI/testing/sysfs-bus-event_source-devices-format
> @@ -9,6 +9,12 @@ Description:
> we want to export, so that userspace can deal with sane
> name/value pairs.
>
> + Userspace must be prepared for the possibility that attributes
> + define overlapping bit ranges. For example:
> + attr1 = 'config:0-23'
> + attr2 = 'config:0-7'
> + attr3 = 'config:12-35'
> +
> Example: 'config1:1,6-10,44'
> Defines contents of attribute that occupies bits 1,6-10,44 of
> perf_event_attr::config1.
> --
> 1.7.10.4
>
prev parent reply other threads:[~2013-05-10 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 4:21 Michael Ellerman
2013-04-08 7:24 ` Michael Ellerman
2013-05-06 1:08 ` Michael Ellerman
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 [this message]
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=20130510152738.GA885@dyad.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@infradead.org \
--cc=jolsa@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@ellerman.id.au \
--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
all inboxes | Powered by JetHome®