From: javier.picorel@epfl.ch (javier.picorel at epfl.ch)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM Cortex A9: LL counters
Date: Wed, 03 Jul 2013 22:32:55 +0200 [thread overview]
Message-ID: <20130703223255.15536gmsbwonw5fb@webmail.epfl.ch> (raw)
Dear all,
It seems that there is no mapping between any ARM Cortex A9 counter to
the L2 (Last Level) access or misses event.
arch/arm/kernel/perf_event_v7.c
[C(LL)] = {
293 [C(OP_READ)] = {
294 [C(RESULT_ACCESS)] = CACHE_OP_UNSUPPORTED,
295 [C(RESULT_MISS)] = CACHE_OP_UNSUPPORTED,
296 },
297 [C(OP_WRITE)] = {
298 [C(RESULT_ACCESS)] = CACHE_OP_UNSUPPORTED,
299 [C(RESULT_MISS)] = CACHE_OP_UNSUPPORTED,
300 },
301 [C(OP_PREFETCH)] = {
302 [C(RESULT_ACCESS)] = CACHE_OP_UNSUPPORTED,
303 [C(RESULT_MISS)] = CACHE_OP_UNSUPPORTED,
304 },
305 },
Looking at ARM's reference manual and OProfile's event list on A9, I
see the following two counters:
CO_LF_MISS: (counter: 1, 2, 3, 4, 5, 6)
Number of coherent linefill requests which miss in all other
CPUs, meaning that the request
is sent to external memory (min count: 500)
CO_LF_HIT: (counter: 1, 2, 3, 4, 5, 6)
Number of coherent linefill requests which hit in another
CPU, meaning that the linefill
data is fetched directly from the relevant cache (min count: 500)
It seems that the first counter refers to the L2 Misses and the second
one to the L2 Hits (Last Level Cache in this architecture). I'm not sure
whether we should do something about this or nor. Thanks!
Best Regards,
Javier
next reply other threads:[~2013-07-03 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 20:32 javier.picorel at epfl.ch [this message]
[not found] <BFCB49997E59134AAAF17FFE77F8FF06673738BC@REXMD.intranet.epfl.ch>
2013-07-04 9:45 ` ARM Cortex A9: LL counters Will Deacon
2013-07-04 23:44 ` Javier Picorel
2013-07-05 10:12 ` Will Deacon
2013-07-06 20:21 ` Javier Picorel
2013-07-08 8:53 ` Will Deacon
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=20130703223255.15536gmsbwonw5fb@webmail.epfl.ch \
--to=javier.picorel@epfl.ch \
--cc=linux-arm-kernel@lists.infradead.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).