From: Mark Brown Date: Wed, 24 Jan 2024 18:12:35 +0000 (+0000) Subject: arm64/sve: Remove bitrotted comment about syscall behaviour X-Git-Tag: v6.9-rc1~114^2~4^7~3 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=b4725d3e460349aa55836a2a128009c578215b90;p=thirdparty%2Fkernel%2Flinux.git arm64/sve: Remove bitrotted comment about syscall behaviour 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 Reviewed-by: Dave Martin Signed-off-by: Mark Brown Link: https://lore.kernel.org/r/20240124-arm64-sve-sme-doc-v2-1-fe3964fb3c19@kernel.org Signed-off-by: Catalin Marinas --- diff --git a/Documentation/arch/arm64/sve.rst b/Documentation/arch/arm64/sve.rst index 0d9a426e9f858..b45a2da19bf1d 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