Skip to content

Commit ff1c42c

Browse files
brooniectmarinas
authored andcommitted
arm64: Explicitly document boot requirements for SVE
We do not currently document the requirements for configuration of the SVE system registers when booting the kernel, let's do so for completeness. We don't have a hard requirement that the vector lengths configured on different CPUs on initial boot be consistent since we have logic to constrain to the minimum supported value but we will reject any late CPUs which can't support the current maximum and introducing the concept of late CPUs seemed more complex than was useful so we require that all CPUs use the same value. Signed-off-by: Mark Brown <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Catalin Marinas <[email protected]>
1 parent b30dbf4 commit ff1c42c

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

Documentation/arm64/booting.rst

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -287,6 +287,24 @@ Before jumping into the kernel, the following conditions must be met:
287287

288288
- CPTR_EL2.TFP (bit 10) must be initialised to 0b0.
289289

290+
For CPUs with the Scalable Vector Extension (FEAT_SVE) present:
291+
292+
- if EL3 is present:
293+
294+
- CPTR_EL3.EZ (bit 8) must be initialised to 0b1.
295+
296+
- ZCR_EL3.LEN must be initialised to the same value for all CPUs the
297+
kernel is executed on.
298+
299+
- If the kernel is entered at EL1 and EL2 is present:
300+
301+
- CPTR_EL2.TZ (bit 8) must be initialised to 0b0.
302+
303+
- CPTR_EL2.ZEN (bits 17:16) must be initialised to 0b11.
304+
305+
- ZCR_EL2.LEN must be initialised to the same value for all CPUs the
306+
kernel will execute on.
307+
290308
The requirements described above for CPU mode, caches, MMUs, architected
291309
timers, coherency and system registers apply to all CPUs. All CPUs must
292310
enter the kernel in the same exception level. Where the values documented

0 commit comments

Comments
 (0)