From: German Gomez <german.gomez@arm.com>
To: Ali Saidi <alisaidi@amazon.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, leo.yan@linaro.org,
acme@kernel.org
Cc: benh@kernel.crashing.org, Nick.Forrington@arm.com,
alexander.shishkin@linux.intel.com, andrew.kilroy@arm.com,
james.clark@arm.com, john.garry@huawei.com, jolsa@kernel.org,
kjain@linux.ibm.com, lihuafei1@huawei.com, mark.rutland@arm.com,
mathieu.poirier@linaro.org, mingo@redhat.com,
namhyung@kernel.org, peterz@infradead.org, will@kernel.org
Subject: Re: [PATCH v3 0/2] perf: arm-spe: Decode SPE source and use for perf c2c
Date: Tue, 22 Mar 2022 12:05:46 +0000 [thread overview]
Message-ID: <cd1abed3-6528-ec8f-260e-dca3654e5ce9@arm.com> (raw)
In-Reply-To: <20220318195913.17459-1-alisaidi@amazon.com>
Hi Ali, thank you for your patches
On 18/03/2022 19:59, Ali Saidi wrote:
> When synthesizing data from SPE, augment the type with source information
> for Arm Neoverse cores so we can detect situtions like cache line contention
> and transfers on Arm platforms.
>
> This changes enables the expected behavior of perf c2c on a system with SPE where
> lines that are shared among multiple cores show up in perf c2c output.
>
> These changes switch to use mem_lvl_num to encode the level information instead
> of mem_lvl which is being deprecated, but I haven't found other users of
> mem_lvl_num.
>
> Changes in v3:
> * Assume ther are only three levels of cache hierarchy
> * Split the mem_lvl_num and HITM changes in c2c into two seperate patches
>
> Ali Saidi (3):
> perf arm-spe: Use SPE data source for neoverse cores
> perf mem: Support mem_lvl_num in c2c command
> perf mem: Support HITM for when mem_lvl_num is any
>
> .../util/arm-spe-decoder/arm-spe-decoder.c | 1 +
> .../util/arm-spe-decoder/arm-spe-decoder.h | 12 ++
> tools/perf/util/arm-spe.c | 109 +++++++++++++++---
> tools/perf/util/mem-events.c | 20 +++-
> 4 files changed, 124 insertions(+), 18 deletions(-)
>
I tested on a Neoverse N1 system using the below commands and the output
looks either unchanged or improved compared to before. For example:
| $ perf mem record -e spe-ldst -a -- sleep 4
| $ perf mem report
|
| 1.39% 1 1263 L3 miss [k] 0xffffb9a34bda2088
| 0.58% 1 529 L1 miss [k] 0xffffb9a34bd3be7c
| 0.34% 1 310 N/A [k] 0xffffb9a34baf4d28
| 0.34% 1 309 N/A [k] 0xffffb9a34bb82844
... became:
| 1.39% 1 1263 RAM hit [k] 0xffffb9a34bda2088
| 0.58% 1 529 L2 hit [k] 0xffffb9a34bd3be7c
| 0.34% 1 310 L1 hit [k] 0xffffb9a34baf4d28
| 0.34% 1 309 L1 hit [k] 0xffffb9a34bb82844
Also some L3 misses are now labeled as "Any cache hit" with the Snoop
bit set. For example:
| 0.37% 1 332 L3 miss [.] 0x0000aaaadf70a700 N/A
... became:
| 0.37% 1 332 Any cache hit [.] 0x0000aaaadf70a700 HitM
Tested-by: German Gomez <german.gomez@arm.com>
Reviewed-by: German Gomez <german.gomez@arm.com>
Thanks,
German
(I didn't run on a non-Neoverse system but it doesn't look like any
behaviour is changed for those)
prev parent reply other threads:[~2022-03-22 12:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 19:59 [PATCH v3 0/2] perf: arm-spe: Decode SPE source and use for perf c2c Ali Saidi
2022-03-18 19:59 ` [PATCH v3 1/3] perf arm-spe: Use SPE data source for neoverse cores Ali Saidi
2022-03-22 21:18 ` Arnaldo Carvalho de Melo
2022-03-18 19:59 ` [PATCH v3 2/3] perf mem: Support mem_lvl_num in c2c command Ali Saidi
2022-03-18 19:59 ` [PATCH v3 3/3] perf mem: Support HITM for when mem_lvl_num is any Ali Saidi
2022-03-22 12:05 ` German Gomez [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=cd1abed3-6528-ec8f-260e-dca3654e5ce9@arm.com \
--to=german.gomez@arm.com \
--cc=Nick.Forrington@arm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=alisaidi@amazon.com \
--cc=andrew.kilroy@arm.com \
--cc=benh@kernel.crashing.org \
--cc=james.clark@arm.com \
--cc=john.garry@huawei.com \
--cc=jolsa@kernel.org \
--cc=kjain@linux.ibm.com \
--cc=leo.yan@linaro.org \
--cc=lihuafei1@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=will@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