From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: icycoder@gmail.com, linux-kernel@vger.kernel.org,
xiaoguangrong@linux.vnet.ibm.com, acme@redhat.com,
paulus@samba.org, Runzhen Wang <runzhen@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/2] perf tools: fix a typo of a Power7 event name
Date: Wed, 19 Jun 2013 19:28:37 -0700 [thread overview]
Message-ID: <20130620022837.GA20609@us.ibm.com> (raw)
In-Reply-To: <1371691282.21846.1.camel@concordia>
Michael Ellerman [michael@ellerman.id.au] wrote:
| On Wed, 2013-06-19 at 17:15 +0800, Runzhen Wang wrote:
| > In the Power7 PMU guide:
| > https://www.power.org/documentation/commonly-used-metrics-for-performance-analysis/
| > PM_BRU_MPRED is referred to as PM_BR_MPRED.
| >
| > This patch fix the typo by changing the name of the event in kernel and
| > documentation accordingly.
| >
| > Signed-off-by: Runzhen Wang <runzhen@linux.vnet.ibm.com>
| > ---
| > .../testing/sysfs-bus-event_source-devices-events | 2 +-
| > arch/powerpc/perf/power7-pmu.c | 12 ++++++------
| > 2 files changed, 7 insertions(+), 7 deletions(-)
| >
| > diff --git a/Documentation/ABI/testing/sysfs-bus-event_source-devices-events b/Documentation/ABI/testing/sysfs-bus-event_source-devices-events
| > index 8b25ffb..3c1cc24 100644
| > --- a/Documentation/ABI/testing/sysfs-bus-event_source-devices-events
| > +++ b/Documentation/ABI/testing/sysfs-bus-event_source-devices-events
| > @@ -29,7 +29,7 @@ Description: Generic performance monitoring events
| >
| > What: /sys/devices/cpu/events/PM_1PLUS_PPC_CMPL
| > /sys/devices/cpu/events/PM_BRU_FIN
| > - /sys/devices/cpu/events/PM_BRU_MPRED
| > + /sys/devices/cpu/events/PM_BR_MPRED
|
| So you're changing the ABI.
|
| I think that's probably OK, but you at least need to mention _why_ you
| think it's OK.
Some of the reasons I think its ok to change:
- It is relatively new interface, specific to the Power7 platform.
- No tools that we know of actually use this interface at this point (none
are listed near the interface).
- Users of this interface (eg oprofile users migrating to perf) would be
more used to the "PM_BR_MPRED" rather than "PM_BRU_MPRED".
- These are in the ABI/testing at this point rather than ABI/stable, so
hoping we have some wiggle room.
But of course this is not a "grave error" or "security hole" which are
the justifications listed in the Documentation/ABI/README. If these
are not good enough reasons, we can leave the misnomer around and
create another file in sysfs with the correct name PM_BR_MPRED.
Sukadev
prev parent reply other threads:[~2013-06-20 2:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 9:15 [PATCH 1/2] perf tools: fix a typo of a Power7 event name Runzhen Wang
2013-06-19 9:15 ` [PATCH 2/2] perf tools: Make Power7 events available for perf Runzhen Wang
2013-06-19 16:14 ` Sukadev Bhattiprolu
2013-06-20 1:41 ` Michael Ellerman
2013-06-20 10:57 ` David Laight
2013-06-19 16:13 ` [PATCH 1/2] perf tools: fix a typo of a Power7 event name Sukadev Bhattiprolu
2013-06-20 1:21 ` Michael Ellerman
2013-06-20 2:28 ` Sukadev Bhattiprolu [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=20130620022837.GA20609@us.ibm.com \
--to=sukadev@linux.vnet.ibm.com \
--cc=acme@redhat.com \
--cc=icycoder@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=paulus@samba.org \
--cc=runzhen@linux.vnet.ibm.com \
--cc=xiaoguangrong@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).