From: James Clark <james.clark@linaro.org>
To: TAKANO Mitsuhiro <takano32@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Jonathan Corbet <corbet@lwn.net>,
Namhyung Kim <namhyung@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH] arm64: perf: Fix the userspace counter example link
Date: Mon, 9 Nov 2026 11:19:53 +0000 [thread overview]
Message-ID: <1baeb4ec-4244-42e0-8c53-29df079c80f6@linaro.org> (raw)
In-Reply-To: <20261106234551.1474417-1-takano32@gmail.com>
On 06/11/2026 23:45, TAKANO Mitsuhiro wrote:
> Documentation/arch/arm64/perf.rst points at
> tools/perf/arch/arm64/tests/user-events.c, in the text and in the link
> target, but the file does not exist: no file of that name is in
> tools/perf/arch/arm64/tests/, and no commit in the history leading to
> this base has added one.
>
> The userspace register access described in this section is covered by
> the "User space counter reading of instructions" and "User space
> counter reading of cycles" cases in tools/perf/tests/mmap-basic.c.
> That file is the only in-tree userspace test that walks the core PMUs,
> pins the test task to each PMU's CPUs, and selects the PMU by its type
> number when the kernel accepts the extended type.
>
> perf test -v user runs the four cases in that file; the two reading
> cases ask for user access through config1.
>
> Point the text and the link target at that file.
>
> make htmldocs does not fetch external links, so a plain documentation
> build does not report it, but make linkcheckdocs does. I checked that
> the old link target returns 404 and the new one returns 200. No kernel
> was built.
>
> The edit and this changelog were written with the help of an LLM
> assistant (Hermes Agent). I reviewed the diff and the reasoning, and I
> am responsible for the submission.
>
> Fixes: aa1005d15d2a ("Documentation: arm64: Document PMU counters access from userspace")
> Signed-off-by: TAKANO Mitsuhiro <takano32@gmail.com>
> ---
> Documentation/arch/arm64/perf.rst | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/arch/arm64/perf.rst b/Documentation/arch/arm64/perf.rst
> index 997fd716b82f..236cb5da425a 100644
> --- a/Documentation/arch/arm64/perf.rst
> +++ b/Documentation/arch/arm64/perf.rst
> @@ -140,9 +140,9 @@ only be enabled when the tasks are pinned to a homogeneous subset of cores and
> the corresponding PMU instance is opened by specifying the 'type' attribute.
> The use of generic event types is not supported in this case.
>
> -Have a look at `tools/perf/arch/arm64/tests/user-events.c`_ for an example. It
> -can be run using the perf tool to check that the access to the registers works
> -correctly from userspace:
> +Have a look at `tools/perf/tests/mmap-basic.c`_ for an example. The two
> +'User space counter reading' tests in it can be run using the perf tool to
> +check that the access to the registers works correctly from userspace:
The section above already says how to use it, and points to the libperf
test as an example.
So this extra reference isn't necessary and is in the "About
heterogeneous systems" anyway which doesn't make sense. Unless it's only
to show how to call sched_setaffinity(), but that's not really in scope.
I would move the sentence about how to run the test into the "How to"
block above and delete the sentence about user-events.c. mmap-basic.c is
also a very confusing test IMO so isn't a good example. That saves one
reference going stale again in the future.
>
> .. code-block:: sh
>
> @@ -160,8 +160,8 @@ userspace must treat the upper 32-bits read from the counter as UNKNOWN. The
> and should be used to mask the upper bits as needed.
>
> .. Links
> -.. _tools/perf/arch/arm64/tests/user-events.c:
> - https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/perf/arch/arm64/tests/user-events.c
> +.. _tools/perf/tests/mmap-basic.c:
> + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/perf/tests/mmap-basic.c
> .. _tools/lib/perf/tests/test-evsel.c:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/lib/perf/tests/test-evsel.c
>
>
> base-commit: d48723711bae9b8cdc56719c448ba42fef28cbee
prev parent reply other threads:[~2026-11-09 11:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 23:45 TAKANO Mitsuhiro
2026-11-09 11:19 ` James Clark [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=1baeb4ec-4244-42e0-8c53-29df079c80f6@linaro.org \
--to=james.clark@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=namhyung@kernel.org \
--cc=takano32@gmail.com \
--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
all inboxes | Powered by JetHome®