From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: Runzhen Wang <runzhen@linux.vnet.ibm.com>
Cc: acme@redhat.com, icycoder@gmail.com,
linux-kernel@vger.kernel.org, xiaoguangrong@linux.vnet.ibm.com,
paulus@samba.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/2] perf tools: Make Power7 events available for perf
Date: Wed, 19 Jun 2013 09:14:46 -0700 [thread overview]
Message-ID: <20130619161446.GB13326@us.ibm.com> (raw)
In-Reply-To: <1371633326-7696-2-git-send-email-runzhen@linux.vnet.ibm.com>
Runzhen Wang [runzhen@linux.vnet.ibm.com] wrote:
| Power7 supports over 530 different perf events but only a small
| subset of these can be specified by name, for the remaining
| events, we must specify them by their raw code:
|
| perf stat -e r2003c <application>
|
| This patch makes all the POWER7 events available in sysfs.
| So we can instead specify these as:
|
| perf stat -e 'cpu/PM_CMPLU_STALL_DFU/' <application>
|
| where PM_CMPLU_STALL_DFU is the r2003c in previous example.
|
| Before this patch is applied, the size of power7-pmu.o is:
|
| $ size arch/powerpc/perf/power7-pmu.o
| text data bss dec hex filename
| 3073 2720 0 5793 16a1 arch/powerpc/perf/power7-pmu.o
|
| and after the patch is applied, it is:
|
| $ size arch/powerpc/perf/power7-pmu.o
| text data bss dec hex filename
| 14451 31112 0 45563 b1fb arch/powerpc/perf/power7-pmu.o
|
| Signed-off-by: Runzhen Wang <runzhen@linux.vnet.ibm.com>
Reviewed-by: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
next prev parent reply other threads:[~2013-06-19 16:15 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 [this message]
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
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=20130619161446.GB13326@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=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).