public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Vince Weaver <vweaver1@eecs.utk.edu>
Cc: linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
	Ingo Molnar <mingo@elte.hu>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	Stephane Eranian <eranian@google.com>,
	Robert Richter <robert.richter@amd.com>
Subject: Re: [patch] perf_events: more wrong events for AMD fam10h
Date: Mon, 27 Jun 2011 13:22:20 +0200	[thread overview]
Message-ID: <1309173740.6701.103.camel@twins> (raw)
In-Reply-To: <alpine.DEB.2.00.1106071532250.21714@cl320.eecs.utk.edu>

On Tue, 2011-06-07 at 15:39 -0400, Vince Weaver wrote:
> Hello
> 
> I'm in the process of auditing perf_event's awesome "generalized events".
> 
> On AMD fam10h for some we have the following definitions:
>   cache-references = INSTRUCTION_CACHE_FETCHES	0x530080
>   cache-misses 	   = INSTRUCTION_CACHE_MISSES	0x530081
> 
> on Intel at least I'm pretty sure these events match to Last Level Cache 
> accesses/misses, not icache.  Is there a reason for this?
> 
> Attached is a patch that removes these until better events can be found.
> (LLC is tricky on AMD as it's a shared resource).
> 
> Note, l1-dcache-stores is broken too, I'm looking into it.
> 
> Thanks,
> 
> Vince
> vweaver1@eecs.utk.edu
> 
> diff --git a/arch/x86/kernel/cpu/perf_event_amd.c b/arch/x86/kernel/cpu/perf_event_amd.c
> index fe29c1d..a46b987 100644
> --- a/arch/x86/kernel/cpu/perf_event_amd.c
> +++ b/arch/x86/kernel/cpu/perf_event_amd.c
> @@ -98,8 +98,6 @@ static const u64 amd_perfmon_event_map[] =
>  {
>    [PERF_COUNT_HW_CPU_CYCLES]			= 0x0076,
>    [PERF_COUNT_HW_INSTRUCTIONS]			= 0x00c0,
> -  [PERF_COUNT_HW_CACHE_REFERENCES]		= 0x0080,
> -  [PERF_COUNT_HW_CACHE_MISSES]			= 0x0081,

Would 0x40000F7E0 and 0x40000F7E1 be better?

>    [PERF_COUNT_HW_BRANCH_INSTRUCTIONS]		= 0x00c2,
>    [PERF_COUNT_HW_BRANCH_MISSES]			= 0x00c3,
>    [PERF_COUNT_HW_STALLED_CYCLES_FRONTEND]	= 0x00d0, /* "Decoder empty" event */


  parent reply	other threads:[~2011-06-27 11:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07 19:39 [patch] perf_events: more wrong events for AMD fam10h Vince Weaver
2011-06-07 21:07 ` [patch] perf_events: even " Vince Weaver
2011-06-27 11:22   ` Peter Zijlstra
2011-06-27 15:51     ` Robert Richter
2011-06-28 16:32       ` Vince Weaver
2011-06-28 16:20     ` Vince Weaver
2011-06-27 11:22 ` Peter Zijlstra [this message]
2011-06-27 13:38   ` [patch] perf_events: " Robert Richter

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=1309173740.6701.103.camel@twins \
    --to=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=robert.richter@amd.com \
    --cc=vweaver1@eecs.utk.edu \
    /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