From: Kevin Brodsky <kevin.brodsky@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Kevin Brodsky <kevin.brodsky@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Brown <broonie@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Will Deacon <will@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] docs: arm64: Document booting requirements for POE at EL0
Date: Thu, 19 Nov 2026 18:02:43 +0000 [thread overview]
Message-ID: <20261119-poe_booting_rst-v1-2-bbae0ab68498@arm.com> (raw)
In-Reply-To: <20261119-poe_booting_rst-v1-0-bbae0ab68498@arm.com>
Add missing boot requirements for the kernel to enable FEAT_S1POE at
EL0 (POE is currently unused at EL1). SCR_EL3.PIEn controls trapping
for both PIE and POE registers.
Suggested-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Kevin Brodsky <kevin.brodsky@arm.com>
---
Documentation/arch/arm64/booting.rst | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/Documentation/arch/arm64/booting.rst b/Documentation/arch/arm64/booting.rst
index 8f22aa7b2c0b..3f31eedd8551 100644
--- a/Documentation/arch/arm64/booting.rst
+++ b/Documentation/arch/arm64/booting.rst
@@ -515,6 +515,18 @@ Before jumping into the kernel, the following conditions must be met:
- HFGRWR_EL2.nPIRE0_EL1 (bit 57) must be initialised to 0b1.
+ For CPUs with the Stage 1 Permission Overlay Extension feature (FEAT_S1POE):
+
+ - If EL3 is present:
+
+ - SCR_EL3.PIEn (bit 45) must be initialised to 0b1.
+
+ - If the kernel is entered at EL1 and EL2 is present:
+
+ - HFGRTR_EL2.nPOR_EL0 (bit 59) must be initialised to 0b1.
+
+ - HFGWTR_EL2.nPOR_EL0 (bit 59) must be initialised to 0b1.
+
For CPUs with Guarded Control Stacks (FEAT_GCS):
- GCSCR_EL1 must be initialised to 0.
--
2.56.0
next prev parent reply other threads:[~2026-11-19 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 18:02 [PATCH 0/2] Add boot requirements for POE + cleanup booting.rst Kevin Brodsky
2026-11-19 18:02 ` [PATCH 1/2] docs: arm64: Fix RST formatting in booting.rst Kevin Brodsky
2026-11-19 19:06 ` Randy Dunlap
2026-11-19 18:02 ` Kevin Brodsky [this message]
2026-11-19 20:17 ` [PATCH 2/2] docs: arm64: Document booting requirements for POE at EL0 Mark Brown
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=20261119-poe_booting_rst-v1-2-bbae0ab68498@arm.com \
--to=kevin.brodsky@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.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=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®