From: Leo Yan <leo.yan@linaro.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
James Clark <james.clark@arm.com>,
German Gomez <german.gomez@arm.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Leo Yan <leo.yan@linaro.org>
Subject: [PATCH] perf arm-spe: Test memory samples
Date: Wed, 13 Apr 2022 09:02:21 +0800 [thread overview]
Message-ID: <20220413010221.81332-1-leo.yan@linaro.org> (raw)
Add a new test to verify the Arm SPE synthesized memory samples with
'perf mem report' command.
Signed-off-by: Leo Yan <leo.yan@linaro.org>
---
tools/perf/tests/shell/test_arm_spe.sh | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/tools/perf/tests/shell/test_arm_spe.sh b/tools/perf/tests/shell/test_arm_spe.sh
index e59044edc406..b36125e127eb 100755
--- a/tools/perf/tests/shell/test_arm_spe.sh
+++ b/tools/perf/tests/shell/test_arm_spe.sh
@@ -62,6 +62,18 @@ perf_report_samples() {
egrep " +[0-9]+\.[0-9]+% +[0-9]+\.[0-9]+% +$1 " > /dev/null 2>&1
}
+perf_mem_report_samples() {
+ echo "Looking at perf.data file for reporting memory samples:"
+
+ # Below is an example of the memory samples reporting:
+ # 20.71% 1696 27 L1 hit [k] el0t_64_sync_handler [kernel.kallsyms] ...
+ # 17.21% 1903 20 L1 hit [k] el0t_64_sync [kernel.kallsyms] ...
+ # 8.52% 897 21 L1 hit [k] ksys_read [kernel.kallsyms] ...
+ # 0.12% 16 17 L1 hit [.] 0x0000000000004ce8 dd ...
+ perf mem report --stdio -i ${perfdata} 2>&1 | \
+ egrep " +[0-9]+\.[0-9]+% +[0-9]+ +[0-9]+ .* +$1 " > /dev/null 2>&1
+}
+
arm_spe_snapshot_test() {
echo "Recording trace with snapshot mode $perfdata"
perf record -o ${perfdata} -e arm_spe// -S \
@@ -79,7 +91,8 @@ arm_spe_snapshot_test() {
wait $PERFPID
perf_script_samples dd &&
- perf_report_samples dd
+ perf_report_samples dd &&
+ perf_mem_report_samples dd
err=$?
arm_spe_report "SPE snapshot testing" $err
--
2.25.1
next reply other threads:[~2022-04-13 1:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 1:02 Leo Yan [this message]
2022-04-13 17:17 ` [PATCH] perf arm-spe: Test memory samples German Gomez
2022-04-14 2:37 ` Leo Yan
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=20220413010221.81332-1-leo.yan@linaro.org \
--to=leo.yan@linaro.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=german.gomez@arm.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@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).