[PATCH v2 1/4] arm64/sve: Remove bitrotted comment about syscall behaviour
Mark Brown
broonie at kernel.org
Wed Jan 24 10:12:35 PST 2024
When we documented that we always clear state not shared with FPSIMD we
didn't catch all of the places that mentioned that state might not be
cleared, remove a lingering reference.
Reported-by: Edmund Grimley-Evans <edmund.grimley-evans at arm.com>
Reviewed-by: Dave Martin <Dave.Martin at arm.com>
Signed-off-by: Mark Brown <broonie at kernel.org>
---
Documentation/arch/arm64/sve.rst | 5 -----
1 file changed, 5 deletions(-)
diff --git a/Documentation/arch/arm64/sve.rst b/Documentation/arch/arm64/sve.rst
index 0d9a426e9f85..b45a2da19bf1 100644
--- a/Documentation/arch/arm64/sve.rst
+++ b/Documentation/arch/arm64/sve.rst
@@ -117,11 +117,6 @@ the SVE instruction set architecture.
* The SVE registers are not used to pass arguments to or receive results from
any syscall.
-* In practice the affected registers/bits will be preserved or will be replaced
- with zeros on return from a syscall, but userspace should not make
- assumptions about this. The kernel behaviour may vary on a case-by-case
- basis.
-
* All other SVE state of a thread, including the currently configured vector
length, the state of the PR_SVE_VL_INHERIT flag, and the deferred vector
length (if any), is preserved across all syscalls, subject to the specific
--
2.30.2
More information about the linux-arm-kernel
mailing list