All of lore.kernel.org
 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 22:27:28 +0100	[thread overview]
Message-ID: <20131224212728.GK20765@two.firstfloor.org> (raw)
In-Reply-To: <52B93B01.4020305@gmail.com>

> I checked what can be measured with the offcore facility. I can ask
> to count remote memory accesses, but now I am not sure PEBS is
> enable for these events. If the answer is no, I can't accurately
> identify remote memory accesses with offcore events ? As a
> consequence I am wondering if there is a way to do such thing ?

The OFFCORE events are not PEBS enabled. However the memory PEBS
events report the same information (with some limitations) in
the PEBS record (and perf reports this information) 

In general you cannot accurately profile all memory accesses.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.

  reply	other threads:[~2013-12-24 21:27 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
2013-12-24  7:42                 ` Manuel Selva
2013-12-24 21:27                   ` Andi Kleen [this message]
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=20131224212728.GK20765@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.