From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [PATCH] perf: Power7: Make CPI stack events available in sysfs
Date: Sat, 11 May 2013 15:31:11 -0700 [thread overview]
Message-ID: <20130511223111.GA30064@us.ibm.com> (raw)
In-Reply-To: <20130422155505.GA26169@us.ibm.com>
Sukadev Bhattiprolu [sukadev@linux.vnet.ibm.com] wrote:
| Michael Ellerman [michael@ellerman.id.au] wrote:
| | On Sat, Apr 06, 2013 at 09:48:03AM -0700, Sukadev Bhattiprolu wrote:
| | > From bdeacf7175241f6c79b5b2be0fa6b20b0d0b7d1c Mon Sep 17 00:00:00 2001
| | > From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
| | > Date: Sat, 6 Apr 2013 08:48:26 -0700
| | > Subject: [PATCH] perf: Power7: Make CPI stack events available in sysfs
| | >
| | > A set of Power7 events are often used for Cycles Per Instruction (CPI) stack
| | > analysis. Make these events available in sysfs (/sys/devices/cpu/events/) so
| | > they can be identified using their symbolic names:
| | >
| | > perf stat -e 'cpu/PM_CMPLU_STALL_DCACHE_MISS/' /bin/ls
| |
| | Should we take these two via the powerpc tree? Or do you want to take
| | them Arnaldo?
|
| I think it can go through powerpc tree since it is all arch-specific.
|
Ben, Paul,
Any comments on this patch ?
https://lkml.org/lkml/2013/4/6/169
next prev parent reply other threads:[~2013-05-11 22:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-06 16:48 [PATCH] perf: Power7: Make CPI stack events available in sysfs Sukadev Bhattiprolu
2013-04-06 17:06 ` [PATCH] perf: Power7 Update testing ABI to list CPI-stack events Sukadev Bhattiprolu
2013-04-15 6:15 ` [PATCH] perf: Power7: Make CPI stack events available in sysfs Michael Ellerman
2013-04-22 15:55 ` Sukadev Bhattiprolu
2013-05-11 22:31 ` Sukadev Bhattiprolu [this message]
2013-05-22 22:23 ` Paul Mackerras
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=20130511223111.GA30064@us.ibm.com \
--to=sukadev@linux.vnet.ibm.com \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=paulus@samba.org \
/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).