From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Carl E. Love" <cel@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org,
Benjamin Herrenschmidt <bherren@au1.ibm.com>,
Paul Mackerras <pmac@au1.ibm.com>
Subject: Re: [PATCH REPOST] perf event, POWER 6: L1 cache read and write access event code fix]
Date: Thu, 29 Sep 2011 17:04:52 +1000 [thread overview]
Message-ID: <1317279892.29415.182.camel@pasglop> (raw)
In-Reply-To: <1317245013.5461.11.camel@oc5652146517.ibm.com>
On Wed, 2011-09-28 at 14:23 -0700, Carl E. Love wrote:
> Ben, Paul:
>
> I posted this patch to lkml but did not copy the linuxppc-dev@ozlabs.org
> mailing list.
Patch is also completely damaged. I'm fixing it up myself this time
around but by now you should know how to send patches correctly :-(
Ben.
> Carl Love
> ---------------------------------------------------------------------
>
> The current L1 cache read event code 0x80082 only counts for thread 0. The
> event code 0x280030 should be used to count events on thread 0 and 1. The
> patch fixes the event code for the L1 cache read.
>
> The current L1 cache write event code 0x80086 only counts for thread 0. The
> event code 0x180032 should be used to count events on thread 0 and 1. The
> patch fixes the event code for the L1 cache write.
>
> FYI, the documentation lists three event codes for the L1 cache read event
> and three event codes for the L1 cache write event. The event description
> for the event codes is as follows:
>
> L1 cache read requests 0x80082 LSU 0 only
> L1 cache read requests 0x8008A LSU 1 only
> L1 cache read requests 0x80030 LSU 1 or LSU 0, counter 2 only.
>
> L1 cache store requests 0x80086 LSU 0 only
> L1 cache store requests 0x8008E LSU 1 only
> L1 cache store requests 0x80032 LSU 0 or LSU 1, counter 1 only.
>
> There can only be one request from either LSU 0 or 1 active at a time.
>
> Signed-off-by: Carl Love <cel@us.ibm.com>
> ---
> arch/powerpc/kernel/power6-pmu.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/powerpc/kernel/power6-pmu.c b/arch/powerpc/kernel/power6-pmu.c
> index 03b95e2..0bbc901 100644
> --- a/arch/powerpc/kernel/power6-pmu.c
> +++ b/arch/powerpc/kernel/power6-pmu.c
> @@ -487,8 +487,8 @@ static int power6_generic_events[] = {
> */
> static int power6_cache_events[C(MAX)][C(OP_MAX)][C(RESULT_MAX)] = {
> [C(L1D)] = { /* RESULT_ACCESS RESULT_MISS */
> - [C(OP_READ)] = { 0x80082, 0x80080 },
> - [C(OP_WRITE)] = { 0x80086, 0x80088 },
> + [C(OP_READ)] = { 0x280030, 0x80080 },
> + [C(OP_WRITE)] = { 0x180032, 0x80088 },
> [C(OP_PREFETCH)] = { 0x810a4, 0 },
> },
> [C(L1I)] = { /* RESULT_ACCESS RESULT_MISS */
>
>
prev parent reply other threads:[~2011-09-29 7:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 21:23 [PATCH REPOST] perf event, POWER 6: L1 cache read and write access event code fix] Carl E. Love
2011-09-29 4:06 ` Paul Mackerras
2011-09-29 7:04 ` Benjamin Herrenschmidt [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=1317279892.29415.182.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=bherren@au1.ibm.com \
--cc=cel@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=pmac@au1.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).