summaryrefslogtreecommitdiffstats
path: root/virt
diff options
context:
space:
mode:
authorSuzuki K Poulose <suzuki.poulose@arm.com>2020-01-13 23:30:19 +0000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-02-14 16:32:23 -0500
commit1e26078c29edb7bdf7d75ddc52d34912b805791e (patch)
tree844682483d8568df5fcf49e37654da66b15aca18 /virt
parentc3f4c5ecf759b55bbabc17a2ff784fcf06ebfb23 (diff)
downloadlinux-stable-1e26078c29edb7bdf7d75ddc52d34912b805791e.tar.gz
linux-stable-1e26078c29edb7bdf7d75ddc52d34912b805791e.tar.bz2
linux-stable-1e26078c29edb7bdf7d75ddc52d34912b805791e.zip
arm64: cpufeature: Fix the type of no FP/SIMD capability
commit 449443c03d8cfdacf7313e17779a2594ebf87e6d upstream. The NO_FPSIMD capability is defined with scope SYSTEM, which implies that the "absence" of FP/SIMD on at least one CPU is detected only after all the SMP CPUs are brought up. However, we use the status of this capability for every context switch. So, let us change the scope to LOCAL_CPU to allow the detection of this capability as and when the first CPU without FP is brought up. Also, the current type allows hotplugged CPU to be brought up without FP/SIMD when all the current CPUs have FP/SIMD and we have the userspace up. Fix both of these issues by changing the capability to BOOT_RESTRICTED_LOCAL_CPU_FEATURE. Fixes: 82e0191a1aa11abf ("arm64: Support systems without FP/ASIMD") Cc: Will Deacon <will@kernel.org> Cc: Mark Rutland <mark.rutland@arm.com> Reviewed-by: Ard Biesheuvel <ardb@kernel.org> Reviewed-by: Catalin Marinas <catalin.marinas@arm.com> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com> Signed-off-by: Will Deacon <will@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions