From: Paul Mackerras <paulus@samba.org>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] perf: Power7: Make CPI stack events available in sysfs
Date: Thu, 23 May 2013 08:23:57 +1000 [thread overview]
Message-ID: <20130522222357.GC10945@iris.ozlabs.ibm.com> (raw)
In-Reply-To: <20130406164803.GA408@us.ibm.com>
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
>
> Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Acked-by: Paul Mackerras <paulus@samba.org>
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mackerras <paulus@samba.org>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf: Power7: Make CPI stack events available in sysfs
Date: Thu, 23 May 2013 08:23:57 +1000 [thread overview]
Message-ID: <20130522222357.GC10945@iris.ozlabs.ibm.com> (raw)
In-Reply-To: <20130406164803.GA408@us.ibm.com>
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
>
> Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Acked-by: Paul Mackerras <paulus@samba.org>
next prev parent reply other threads:[~2013-05-22 22:23 UTC|newest]
Thread overview: 14+ 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 16:48 ` Sukadev Bhattiprolu
2013-04-06 17:06 ` [PATCH] perf: Power7 Update testing ABI to list CPI-stack events Sukadev Bhattiprolu
2013-04-06 17:06 ` Sukadev Bhattiprolu
2013-05-31 12:24 ` [tip:perf/core] " tip-bot for Sukadev Bhattiprolu
2013-04-15 6:15 ` [PATCH] perf: Power7: Make CPI stack events available in sysfs Michael Ellerman
2013-04-15 6:15 ` Michael Ellerman
2013-04-22 15:55 ` Sukadev Bhattiprolu
2013-04-22 15:55 ` Sukadev Bhattiprolu
2013-05-11 22:31 ` Sukadev Bhattiprolu
2013-05-11 22:31 ` Sukadev Bhattiprolu
2013-05-22 22:23 ` Paul Mackerras [this message]
2013-05-22 22:23 ` Paul Mackerras
2013-05-31 12:22 ` [tip:perf/core] " tip-bot for 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=20130522222357.GC10945@iris.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sukadev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.