From c9d22fd9ef7210c4a7e5fafa1a358a0760ba340e Mon Sep 17 00:00:00 2001 From: Will Deacon Date: Thu, 7 Jul 2022 15:52:12 +0100 Subject: [PATCH] Revert "FROMGIT: arm64/fpsimd: Document the use of TIF_FOREIGN_FPSTATE by KVM" This reverts commit 2e202f384916509379e4a923005cadbd8c2ff6f1. Bug: 233587962 Signed-off-by: Will Deacon Change-Id: Iab9a6f03411550b9cb35074f721262c31ea6b70e --- arch/arm64/kernel/fpsimd.c | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/arch/arm64/kernel/fpsimd.c b/arch/arm64/kernel/fpsimd.c index 1fbd6ba7dbac..ff4962750b3d 100644 --- a/arch/arm64/kernel/fpsimd.c +++ b/arch/arm64/kernel/fpsimd.c @@ -78,11 +78,7 @@ * indicate whether or not the userland FPSIMD state of the current task is * present in the registers. The flag is set unless the FPSIMD registers of this * CPU currently contain the most recent userland FPSIMD state of the current - * task. If the task is behaving as a VMM, then this is will be managed by - * KVM which will clear it to indicate that the vcpu FPSIMD state is currently - * loaded on the CPU, allowing the state to be saved if a FPSIMD-aware - * softirq kicks in. Upon vcpu_put(), KVM will save the vcpu FP state and - * flag the register state as invalid. + * task. * * In order to allow softirq handlers to use FPSIMD, kernel_neon_begin() may * save the task's FPSIMD context back to task_struct from softirq context.