From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: James Clark <james.clark@arm.com>
Cc: linux-perf-users@vger.kernel.or, linux-kernel@vger.kernel.org,
leo.yan@linaro.com, 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>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf mem/c2c: Document that SPE is used for mem and c2c on Arm
Date: Tue, 24 Jan 2023 15:37:10 -0300 [thread overview]
Message-ID: <Y9AlVmA+dZLm2uwi@kernel.org> (raw)
In-Reply-To: <20230124145929.557891-1-james.clark@arm.com>
Em Tue, Jan 24, 2023 at 02:59:29PM +0000, James Clark escreveu:
> Setup is non-trivial so also link to the full SPE docs.
Thanks, applied.
- Arnaldo
> Signed-off-by: James Clark <james.clark@arm.com>
> ---
> tools/perf/Documentation/perf-c2c.txt | 8 ++++++--
> tools/perf/Documentation/perf-mem.txt | 7 ++++++-
> 2 files changed, 12 insertions(+), 3 deletions(-)
>
> diff --git a/tools/perf/Documentation/perf-c2c.txt b/tools/perf/Documentation/perf-c2c.txt
> index af5c3106f468..4e8c263e1721 100644
> --- a/tools/perf/Documentation/perf-c2c.txt
> +++ b/tools/perf/Documentation/perf-c2c.txt
> @@ -22,7 +22,11 @@ you to track down the cacheline contentions.
> On Intel, the tool is based on load latency and precise store facility events
> provided by Intel CPUs. On PowerPC, the tool uses random instruction sampling
> with thresholding feature. On AMD, the tool uses IBS op pmu (due to hardware
> -limitations, perf c2c is not supported on Zen3 cpus).
> +limitations, perf c2c is not supported on Zen3 cpus). On Arm64 it uses SPE to
> +sample load and store operations, therefore hardware and kernel support is
> +required. See linkperf:perf-arm-spe[1] for a setup guide. Due to the
> +statistical nature of Arm SPE sampling, not every memory operation will be
> +sampled.
>
> These events provide:
> - memory address of the access
> @@ -333,4 +337,4 @@ Check Joe's blog on c2c tool for detailed use case explanation:
>
> SEE ALSO
> --------
> -linkperf:perf-record[1], linkperf:perf-mem[1]
> +linkperf:perf-record[1], linkperf:perf-mem[1], linkperf:perf-arm-spe[1]
> diff --git a/tools/perf/Documentation/perf-mem.txt b/tools/perf/Documentation/perf-mem.txt
> index 005c95580b1e..19862572e3f2 100644
> --- a/tools/perf/Documentation/perf-mem.txt
> +++ b/tools/perf/Documentation/perf-mem.txt
> @@ -23,6 +23,11 @@ Note that on Intel systems the memory latency reported is the use-latency,
> not the pure load (or store latency). Use latency includes any pipeline
> queueing delays in addition to the memory subsystem latency.
>
> +On Arm64 this uses SPE to sample load and store operations, therefore hardware
> +and kernel support is required. See linkperf:perf-arm-spe[1] for a setup guide.
> +Due to the statistical nature of SPE sampling, not every memory operation will
> +be sampled.
> +
> OPTIONS
> -------
> <command>...::
> @@ -93,4 +98,4 @@ all perf record options.
>
> SEE ALSO
> --------
> -linkperf:perf-record[1], linkperf:perf-report[1]
> +linkperf:perf-record[1], linkperf:perf-report[1], linkperf:perf-arm-spe[1]
>
> base-commit: 5670ebf54bd26482f57a094c53bdc562c106e0a9
> --
> 2.39.1
>
--
- Arnaldo
prev parent reply other threads:[~2023-01-24 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 14:59 [PATCH] perf mem/c2c: Document that SPE is used for mem and c2c on Arm James Clark
2023-01-24 18:37 ` Arnaldo Carvalho de Melo [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=Y9AlVmA+dZLm2uwi@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@linaro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.or \
--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).