From: Huang Shijie <shijie@os.amperecomputing.com>
To: catalin.marinas@arm.com, will@kernel.org, corbet@lwn.net
Cc: patches@amperecomputing.com, cl@linux.com,
yang@os.amperecomputing.com, akpm@linux-foundation.org,
paulmck@kernel.org, rostedt@goodmis.org, Neeraj.Upadhyay@amd.com,
bp@alien8.de, ardb@kernel.org, anshuman.khandual@arm.com,
suzuki.poulose@arm.com, gshan@redhat.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, rdunlap@infradead.org,
Huang Shijie <shijie@os.amperecomputing.com>
Subject: [PATCH V6 0/2] arm64: refactor the rodata=xxx
Date: Thu, 3 Jul 2025 17:42:10 +0800 [thread overview]
Message-ID: <20250703094212.20294-1-shijie@os.amperecomputing.com> (raw)
From Documentation/admin-guide/kernel-parameters.txt, we know that:
rodata= [KNL,EARLY]
on Mark read-only kernel memory as read-only (default).
off Leave read-only kernel memory writable for debugging.
full Mark read-only kernel memory and aliases as read-only
[arm64]
So the "rodata=on" is the default.
But the current code does not follow the document, it makes "rodata=full"
as the default.
This patch set follows Anshuman Khandual's suggetions.
It makes the "rodata=on" as the default, and removes
the CONFIG_RODATA_FULL_DEFAULT_ENABLED.
v6:
Fix a small issue pointed by Randy Dunlap.
v5:
Rebase this patch set with linux-next20250627
https://lists.infradead.org/pipermail/linux-arm-kernel/2025-June/1040297.html
v4:
Follows Anshuman Khandual/Ard Biesheuvel's suggetions:
- Change commit message format.
- Change the titile name.
- others
https://lists.infradead.org/pipermail/linux-arm-kernel/2024-December/985629.html
v3:
Follows Anshuman Khandual's suggetions:
- Merge patch 1 and patch 3 into one patch.
- Remove patch 4
- update comments and document.
https://lists.infradead.org/pipermail/linux-arm-kernel/2024-December/984344.html
v2:
Follows Will's suggetions.
Add a new file fine-tuning-tips.rst for the expert users.
https://lists.infradead.org/pipermail/linux-arm-kernel/2024-November/981190.html
v1:
https://lists.infradead.org/pipermail/linux-arm-kernel/2024-October/971415.html
Huang Shijie (2):
arm64: refactor the rodata=xxx
arm64/Kconfig: Remove CONFIG_RODATA_FULL_DEFAULT_ENABLED
.../admin-guide/kernel-parameters.txt | 2 +-
arch/arm64/Kconfig | 14 ----------
arch/arm64/include/asm/setup.h | 28 +++++++++++++++++--
arch/arm64/mm/pageattr.c | 2 +-
4 files changed, 28 insertions(+), 18 deletions(-)
--
2.40.1
next reply other threads:[~2025-07-03 9:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 9:42 Huang Shijie [this message]
2025-07-03 9:42 ` [PATCH V6 1/2] arm64: refactor the rodata=xxx Huang Shijie
2025-09-08 11:35 ` Will Deacon
2025-09-09 2:52 ` Shijie Huang
2025-07-03 9:42 ` [PATCH V6 2/2] arm64/Kconfig: Remove CONFIG_RODATA_FULL_DEFAULT_ENABLED Huang Shijie
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=20250703094212.20294-1-shijie@os.amperecomputing.com \
--to=shijie@os.amperecomputing.com \
--cc=Neeraj.Upadhyay@amd.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=cl@linux.com \
--cc=corbet@lwn.net \
--cc=gshan@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@amperecomputing.com \
--cc=paulmck@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yang@os.amperecomputing.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