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: [RFC/PATCH] perf: Expand definition of sysfs format attribute
Date: Mon, 4 Mar 2013 15:21:05 +1100 [thread overview]
Message-ID: <1362370865-4437-1-git-send-email-michael@ellerman.id.au> (raw)
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>
---
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
next reply other threads:[~2013-03-04 4:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 4:21 Michael Ellerman [this message]
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
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=1362370865-4437-1-git-send-email-michael@ellerman.id.au \
--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
all inboxes | Powered by JetHome®