From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>, Jiri Olsa <jolsa@redhat.com>
Cc: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
Will Deacon <Will.Deacon@arm.com>
Subject: Re: [PATCH] arc: perf: Enable generic "cache-references" and "cache-misses" events
Date: Wed, 31 Aug 2016 12:05:14 -0700 [thread overview]
Message-ID: <5f65fa04-8d33-e525-115d-4e6991a7668e@synopsys.com> (raw)
In-Reply-To: <6074e252-6e18-bb01-4de1-023bd7e82f03@synopsys.com>
On 08/26/2016 10:31 AM, Vineet Gupta wrote:
> On 08/25/2016 04:49 AM, Alexey Brodkin wrote:
>> ...
>> [PERF_COUNT_ARC_EDTLB] = "edtlb", /* D-TLB Miss */
>> [PERF_COUNT_ARC_EITLB] = "eitlb", /* I-TLB Miss */
>> +
>> + [PERF_COUNT_HW_CACHE_REFERENCES] = "imemrdc", /* Instr: mem read cached */
>> + [PERF_COUNT_HW_CACHE_MISSES] = "dclm", /* D-cache Load Miss */
> I think this is duplicating a mistake we already have. I vaguely remember when
> doing some hackbench profiling last year with range based profiling confined to
> memset routine and saw that L1-dcache-misses was counting zero. This is because it
> only counts LD misses while memset only does ST.
>
> Performance counter stats for '/sbin/hackbench':
>
> 0 L1-dcache-misses
> 0 L1-dcache-load-misses
> 1846082 L1-dcache-store-misses
>
>
> @PeterZ do you concur that is wrong and we ought to setup 2 counters to do this
> correctly ?
Hi Peter / Will,
Can you provide some guidance here. So I looked at what others do -
ARMV7_PERFCTR_L1_DCACHE_REFILL counts both load and store misses, while ARC has 2
separate conditions for load or stores. Is there an existing mechanism to "group"
/ "add" them to give a cumulative PERF_COUNT_HW_CACHE_MISSES - is that what perf
event grouping is ?
Quoting from perf wiki @ https://perf.wiki.kernel.org/index.php/Tutorial
"It can be interesting to try and pack events in a way that guarantees that event
A and B are always measured together. Although the perf_events kernel interface
provides support for event grouping, the current perf tool does *not*."
Thx,
-Vineet
next parent reply other threads:[~2016-08-31 19:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1472125647-518-1-git-send-email-abrodkin@synopsys.com>
[not found] ` <6074e252-6e18-bb01-4de1-023bd7e82f03@synopsys.com>
2016-08-31 19:05 ` Vineet Gupta [this message]
2016-09-01 8:33 ` [PATCH] arc: perf: Enable generic "cache-references" and "cache-misses" events Peter Zijlstra
2016-09-20 20:56 ` perf event grouping for dummies (was Re: [PATCH] arc: perf: Enable generic "cache-references" and "cache-misses" events) Vineet Gupta
2016-09-22 0:43 ` Paul Clarke
2016-09-22 7:56 ` Peter Zijlstra
2016-09-22 17:50 ` Vineet Gupta
2016-09-22 18:23 ` Paul Clarke
2016-09-22 19:42 ` Arnaldo Carvalho de Melo
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=5f65fa04-8d33-e525-115d-4e6991a7668e@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Will.Deacon@arm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-snps-arc@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).