From: Huang Shijie <shijie@os.amperecomputing.com>
To: catalin.marinas@arm.com, will@kernel.org
Cc: patches@amperecomputing.com, paulmck@kernel.org,
akpm@linux-foundation.org, thuth@redhat.com, rostedt@goodmis.org,
xiongwei.song@windriver.com, ardb@kernel.org,
steven.price@arm.com, suzuki.poulose@arm.com,
mark.rutland@arm.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, cl@os.amperecomputing.com,
Huang Shijie <shijie@os.amperecomputing.com>
Subject: [PATCH v2 0/4] arm64: refactor the rodata=xxx
Date: Tue, 26 Nov 2024 16:56:43 +0800 [thread overview]
Message-ID: <20241126085647.4993-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 Will's suggetions:
- Make our "on" behaviour be what is currently done by "full"
- Remove RODATA_FULL_DEFAULT_ENABLED
- Introduce a new option (e.g. "rodata=noalias") which would match the
current "on" behaviour
- Update (simplify) the documentation
https://lists.infradead.org/pipermail/linux-arm-kernel/2024-October/972613.html
v2:
Follows Will's suggetions.
Add a new file fine-tuning-tips.rst for the expert users.
v1:
https://lists.infradead.org/pipermail/linux-arm-kernel/2024-October/971415.html
Huang Shijie (4):
arm64: make rodata=on behaviour be the original rodata=full
arm64: remove CONFIG_RODATA_FULL_DEFAULT_ENABLED
arm64: introduce rodata=noalias
arm64: add a new document for the fine-tuning tips
.../admin-guide/kernel-parameters.txt | 2 +-
Documentation/arch/arm64/fine-tuning-tips.rst | 23 +++++++++++++++++++
Documentation/arch/arm64/index.rst | 1 +
arch/arm64/Kconfig | 14 -----------
arch/arm64/include/asm/setup.h | 4 ++--
arch/arm64/mm/pageattr.c | 2 +-
6 files changed, 28 insertions(+), 18 deletions(-)
create mode 100644 Documentation/arch/arm64/fine-tuning-tips.rst
--
2.40.1
next reply other threads:[~2024-11-26 8:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 8:56 Huang Shijie [this message]
2024-11-26 8:56 ` [PATCH v2 1/4] arm64: make rodata=on behaviour be the original rodata=full Huang Shijie
2024-12-06 4:21 ` Anshuman Khandual
2024-11-26 8:56 ` [PATCH v2 2/4] arm64: remove CONFIG_RODATA_FULL_DEFAULT_ENABLED Huang Shijie
2024-12-06 4:40 ` Anshuman Khandual
2024-11-26 8:56 ` [PATCH v2 3/4] arm64: introduce rodata=noalias Huang Shijie
2024-12-06 4:29 ` Anshuman Khandual
2024-12-06 5:50 ` Shijie Huang
2024-11-26 8:56 ` [PATCH v2 4/4] arm64: add a new document for the fine-tuning tips Huang Shijie
2024-12-02 19:19 ` Christoph Lameter
2024-12-06 3:23 ` [PATCH v2 4/4 fix] " Huang Shijie
2024-12-06 3:56 ` [PATCH v2 4/4] " Anshuman Khandual
2024-12-06 6:14 ` Shijie Huang
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=20241126085647.4993-1-shijie@os.amperecomputing.com \
--to=shijie@os.amperecomputing.com \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cl@os.amperecomputing.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=patches@amperecomputing.com \
--cc=paulmck@kernel.org \
--cc=rostedt@goodmis.org \
--cc=steven.price@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=thuth@redhat.com \
--cc=will@kernel.org \
--cc=xiongwei.song@windriver.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