linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Anshuman Khandual <khandual@linux.vnet.ibm.com>
Cc: Linux PPC dev <linuxppc-dev@ozlabs.org>,
	Michael Ellerman <ellerman@au1.ibm.com>,
	Michael Neuling <michael.neuling@au1.ibm.com>
Subject: Re: [PATCH] powerpc, perf: Add generic cache reference and cache miss events for POWER8 PMU
Date: Mon, 8 Jul 2013 18:28:45 +1000	[thread overview]
Message-ID: <20130708082844.GA18271@concordia> (raw)
In-Reply-To: <51D11DEF.8070302@linux.vnet.ibm.com>

On Mon, Jul 01, 2013 at 11:43:03AM +0530, Anshuman Khandual wrote:
> powerpc, perf: Add generic cache reference and cache miss events for POWER8 PMU
> 
> This enables generic cache reference and cache miss events on POWER8 systems by
> utilizing raw PMU event codes for L1 cache reference and L1 cache miss events
> respectively.
> 
> Signed-off-by: Anshuman Khandual <khandual@linux.vnet.ibm.com>
> 
> diff --git a/arch/powerpc/perf/power8-pmu.c b/arch/powerpc/perf/power8-pmu.c
> index f7d1c4f..5ccddac 100644
> --- a/arch/powerpc/perf/power8-pmu.c
> +++ b/arch/powerpc/perf/power8-pmu.c
> @@ -24,6 +24,8 @@
>  #define PM_INST_CMPL			0x00002
>  #define PM_BRU_FIN			0x10068
>  #define PM_BR_MPRED_CMPL		0x400f6
> +#define PM_LD_MISS_L1			0x3E054
> +#define PM_LD_REF_L1			0x100EE

Hi Anshuman,

Which system did you test this on and what results did you see?

cheers

  reply	other threads:[~2013-07-08  8:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01  6:13 [PATCH] powerpc, perf: Add generic cache reference and cache miss events for POWER8 PMU Anshuman Khandual
2013-07-08  8:28 ` Michael Ellerman [this message]
2013-07-09  7:55   ` Anshuman Khandual

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=20130708082844.GA18271@concordia \
    --to=michael@ellerman.id.au \
    --cc=ellerman@au1.ibm.com \
    --cc=khandual@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michael.neuling@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).