linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Manuel Selva <selva.manuel@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>, linux-perf-users@vger.kernel.org
Subject: Re: Understanding perf mem -t load results
Date: Tue, 24 Dec 2013 08:28:13 +0100	[thread overview]
Message-ID: <20131224072813.GI20765@two.firstfloor.org> (raw)
In-Reply-To: <52B93352.2030909@gmail.com>

On Tue, Dec 24, 2013 at 08:10:10AM +0100, Manuel Selva wrote:
> "You cannot use uncore events to sample IPs" means that the values
> corresponding to PERF_SAMPLE_IP are not correct ? Some benchmarks I
> did by sampling ME_INST_RETIRED with PERF_SAMPLE_IP let me think
> that I was able to get the source of th event. The IP value was
> coherent. Maybe this is not always the case.

It's the IP of a random core on the socket that happens to read the uncore
registers.

-Andi

  reply	other threads:[~2013-12-24  7:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-12 14:06 Understanding perf mem -t load results Manuel Selva
2013-12-15 18:27 ` Manuel Selva
2013-12-15 21:18 ` Andi Kleen
2013-12-15 22:03   ` Manuel Selva
2013-12-15 23:45     ` Andi Kleen
2013-12-16  9:13       ` Manuel Selva
2013-12-20  9:38         ` Manuel Selva
2013-12-24  2:18           ` Andi Kleen
2013-12-24  7:10             ` Manuel Selva
2013-12-24  7:28               ` Andi Kleen [this message]
2013-12-24  7:42                 ` Manuel Selva
2013-12-24 21:27                   ` Andi Kleen
2013-12-25 10:25                     ` Manuel Selva
2014-01-07 15:06                       ` Manuel Selva
2014-01-07 21:27                         ` Andi Kleen
2014-01-08  8:53                           ` Manuel Selva
2014-01-08  9:50                             ` Manuel Selva
2014-01-08 19:44                             ` Andi Kleen

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=20131224072813.GI20765@two.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=selva.manuel@gmail.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).