From: Harald Servat <harald.servat@bsc.es>
To: "linux-perf-users@vger.kernel.org" <linux-perf-users@vger.kernel.org>
Subject: Re: Sample LLC miss references?
Date: Thu, 08 Jan 2015 10:08:00 +0100 [thread overview]
Message-ID: <54AE48F0.6070702@bsc.es> (raw)
In-Reply-To: <54A295A5.9030408@bsc.es>
On 30/12/14 13:08, Harald Servat wrote:
> Dear list,
>
> I'd like to use PEBS to sample only misses at LLC on my Intel(R)
> Core(TM) i7-2760QM CPU.
>
> I've been digging into section 18.4.4 of the Intel® 64 and IA-32
> Architectures Developer's Manual: Vol. 3B and I've found that
> MEM_LOAD_RETIRED does not include LLC_MISSES in that event. However, in
> Table 19-13 (Section 19.6) the LLC_MISSES can be reported by setting
> umask 0x10. Since I'm interested on this particular counter, I guess
> that I cannot use perf mem command and I've have to stick with perf, am
> I right?
>
> In order to test this, I've modified the stream benchmark so that the
> accesses are random in each of the four kernels (copy, scale, add and
> triad) in order to reduce the spatial&temporal localities.
>
> So if I run
>
> # Capture MEM_LOAD_RETIRED.L2_HIT
> perf record -c 1 -e r02cb ./stream.rand
>
> The number of captured samples is about 2M.
>
> However, if I run
>
> # Capture MEM_LOAD_RETIRED.L3_MISS
> perf record -c 1 -e r10cb ./stream.rand
>
> then I get 0 samples. Is that a demonstration that it's impossible to
> capture precise misses at L3? If so, is there any alternative to do
> that? Could I use the latency to bring the data from the memory
> hierarchy instead?
>
> Thank you very much, and happy new year!
>
Any thoughts on this?
Thank you very much.
WARNING / LEGAL TEXT: This message is intended only for the use of the
individual or entity to which it is addressed and may contain
information which is privileged, confidential, proprietary, or exempt
from disclosure under applicable law. If you are not the intended
recipient or the person responsible for delivering the message to the
intended recipient, you are strictly prohibited from disclosing,
distributing, copying, or in any way using this message. If you have
received this communication in error, please notify the sender and
destroy and delete any copies you may have received.
http://www.bsc.es/disclaimer
prev parent reply other threads:[~2015-01-08 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 12:08 Sample LLC miss references? Harald Servat
2015-01-08 9:08 ` Harald Servat [this message]
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=54AE48F0.6070702@bsc.es \
--to=harald.servat@bsc.es \
--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).