From: Joel Granados <joel.granados@kernel.org>
To: Kees Cook <kees@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-riscv@lists.infradead.org,
Joel Granados <joel.granados@kernel.org>
Subject: [PATCH 6/6] docs: Downgrade arm64 & riscv from titles to comment
Date: Tue, 01 Jul 2025 10:56:47 +0200 [thread overview]
Message-ID: <20250701-jag-sysctldoc-v1-6-936912553f58@kernel.org> (raw)
In-Reply-To: <20250701-jag-sysctldoc-v1-0-936912553f58@kernel.org>
Remove the title string ("====") from under arm64 & riscv and move them
to a commment under the perf_user_access sysctl. They are explanations,
*not* sysctls themselves
This effectively removes these two strings from appearing as not
implemented when the check-sysctl-docs script is run
Signed-off-by: Joel Granados <joel.granados@kernel.org>
---
Documentation/admin-guide/sysctl/kernel.rst | 32 +++++++++++++----------------
1 file changed, 14 insertions(+), 18 deletions(-)
diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
index dd49a89a62d3542fa1a599f318dff26589e1d57b..c2683ce17b25821559d0c04914aea360440c7309 100644
--- a/Documentation/admin-guide/sysctl/kernel.rst
+++ b/Documentation/admin-guide/sysctl/kernel.rst
@@ -1014,30 +1014,26 @@ perf_user_access (arm64 and riscv only)
Controls user space access for reading perf event counters.
-arm64
-=====
+* for arm64
+ The default value is 0 (access disabled).
-The default value is 0 (access disabled).
+ When set to 1, user space can read performance monitor counter registers
+ directly.
-When set to 1, user space can read performance monitor counter registers
-directly.
+ See Documentation/arch/arm64/perf.rst for more information.
-See Documentation/arch/arm64/perf.rst for more information.
+* for riscv
+ When set to 0, user space access is disabled.
-riscv
-=====
+ The default value is 1, user space can read performance monitor counter
+ registers through perf, any direct access without perf intervention will trigger
+ an illegal instruction.
-When set to 0, user space access is disabled.
+ When set to 2, which enables legacy mode (user space has direct access to cycle
+ and insret CSRs only). Note that this legacy value is deprecated and will be
+ removed once all user space applications are fixed.
-The default value is 1, user space can read performance monitor counter
-registers through perf, any direct access without perf intervention will trigger
-an illegal instruction.
-
-When set to 2, which enables legacy mode (user space has direct access to cycle
-and insret CSRs only). Note that this legacy value is deprecated and will be
-removed once all user space applications are fixed.
-
-Note that the time CSR is always directly accessible to all modes.
+ Note that the time CSR is always directly accessible to all modes.
pid_max
=======
--
2.47.2
next prev parent reply other threads:[~2025-07-01 8:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 8:56 [PATCH 0/6] docs: Remove false positives from check-sysctl-docs Joel Granados
2025-07-01 8:56 ` [PATCH 1/6] docs: nixify check-sysctl-docs Joel Granados
2025-07-01 8:56 ` [PATCH 2/6] docs: Use skiplist when checking sysctl admin-guide Joel Granados
2025-07-01 8:56 ` [PATCH 3/6] docs: Add awk section for ucount sysctl entries Joel Granados
2025-07-01 8:56 ` [PATCH 4/6] docs: Remove colon from ctltable title in vm.rst Joel Granados
2025-07-01 8:56 ` [PATCH 5/6] docs: Replace spaces with tabs in check-sysctl-docs Joel Granados
2025-07-01 8:56 ` Joel Granados [this message]
2025-08-10 21:12 ` [PATCH 0/6] docs: Remove false positives from check-sysctl-docs patchwork-bot+linux-riscv
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=20250701-jag-sysctldoc-v1-6-936912553f58@kernel.org \
--to=joel.granados@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=corbet@lwn.net \
--cc=kees@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
/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).