From: Manuel Selva <selva.manuel@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Understanding perf mem -t load results
Date: Wed, 25 Dec 2013 11:25:44 +0100 [thread overview]
Message-ID: <52BAB2A8.1040709@gmail.com> (raw)
In-Reply-To: <20131224212728.GK20765@two.firstfloor.org>
On 12/24/2013 10:27 PM, Andi Kleen wrote:
>> 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.
Ok, you confirm what I read in the Intel SDM.
However the memory PEBS
> events report the same information (with some limitations) in
> the PEBS record (and perf reports this information)
By memory PEBS events, do you mean the following events ?
MEM_LOAD_RETIRED.L1D_MISS
MEM_LOAD_RETIRED.L1D_LINE_MISS
MEM_LOAD_RETIRED.L2_MISS
MEM_LOAD_RETIRED.L2_LINE_MISS
MEM_LOAD_RETIRED.DTLB_MISS
I can't profile memory accesses with these events, isn't it ? What do
you mean by perf reports this infomation, which perf tool ?
>
> In general you cannot accurately profile all memory accesses.
Does it means that the perf mem record tool is reporting wrong values
concerning the source of the event ? (I checked that this tool use the
load latency event with PEBS and you said that the IP reported by this
uncore event is not always the correct one ?)
Thanks,
----
Manu
next prev parent reply other threads:[~2013-12-25 10:25 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
2013-12-25 10:25 ` Manuel Selva [this message]
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=52BAB2A8.1040709@gmail.com \
--to=selva.manuel@gmail.com \
--cc=andi@firstfloor.org \
--cc=linux-perf-users@vger.kernel.org \
/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).