[ Sasha's backport helper bot ]
Hi,
Summary of potential issues: ⚠️ Found follow-up fixes in mainline
The upstream commit SHA1 provided is correct: 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe
Status in newer kernel trees: 6.14.y | Present (exact SHA1) 6.13.y | Present (exact SHA1) 6.12.y | Present (exact SHA1) 6.6.y | Present (exact SHA1)
Found fixes commits: fbc7e61195e2 KVM: arm64: Unconditionally save+flush host FPSIMD/SVE/SME state
Note: The patch differs from the upstream commit: --- 1: 93ae6b01bafee ! 1: 4f6496e37d54f KVM: arm64: Discard any SVE state when entering KVM guests @@ Metadata ## Commit message ## KVM: arm64: Discard any SVE state when entering KVM guests
+ [ Upstream commit 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe ] + Since 8383741ab2e773a99 (KVM: arm64: Get rid of host SVE tracking/saving) KVM has not tracked the host SVE state, relying on the fact that we currently disable SVE whenever we perform a syscall. This may not be true @@ Commit message Reviewed-by: Marc Zyngier maz@kernel.org Link: https://lore.kernel.org/r/20221115094640.112848-2-broonie@kernel.org Signed-off-by: Will Deacon will@kernel.org + [ Mark: trivial backport to v6.1 ] + Signed-off-by: Mark Rutland mark.rutland@arm.com + Signed-off-by: Mark Brown broonie@kernel.org
## arch/arm64/include/asm/fpsimd.h ## @@ arch/arm64/include/asm/fpsimd.h: extern void fpsimd_signal_preserve_current_state(void); ---
Results of testing on various branches:
| Branch | Patch Apply | Build Test | |---------------------------|-------------|------------| | stable/linux-6.1.y | Success | Success |