public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Vince Weaver <vweaver1@eecs.utk.edu>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] perf wrong branches event on AMD
Date: Thu, 1 Jul 2010 16:54:40 -0300	[thread overview]
Message-ID: <20100701195439.GJ4078@ghostprotocols.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1007011526010.23160@cl320.eecs.utk.edu>

Em Thu, Jul 01, 2010 at 03:30:16PM -0400, Vince Weaver escreveu:
> Hello
> 
> while doing some performance counter validation tests on some assembly 
> language programs I noticed that the "branches:u" count was very wrong on 
> AMD machines.
> 
> It looks like the wrong event was selected.
> 
> This is why event selection needs to be in user-space... it could be fixed 
> instantly there, but the way things are done now it will take months to 
> years for this fix to filter down to those trying to use perf counters...

Well, you can use:

  rNNN (see 'perf list --help' on how to encode it) [Raw hardware event descriptor]

In the meantime.

- Arnaldo

  reply	other threads:[~2010-07-01 19:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-01 19:30 [PATCH] perf wrong branches event on AMD Vince Weaver
2010-07-01 19:54 ` Arnaldo Carvalho de Melo [this message]
2010-07-02 11:38 ` Peter Zijlstra
2010-07-02 13:56   ` Vince Weaver
2010-07-02 14:23     ` Peter Zijlstra
2010-07-02 19:52       ` Vince Weaver
2010-07-03 13:54         ` Ingo Molnar
2010-07-04  0:30           ` David Dillow
2010-07-04  9:11             ` Ingo Molnar
2010-07-03 13:58 ` [tip:perf/urgent] perf, x86: Fix incorrect branches event on AMD CPUs tip-bot for Vince Weaver

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=20100701195439.GJ4078@ghostprotocols.net \
    --to=acme@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --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