diff options
| author |   Mark Brown <broonie@kernel.org> | 2025-04-17 00:32:49 +0100 |
|---|---|---|
| committer |   Marc Zyngier <maz@kernel.org> | 2025-05-06 09:50:56 +0100 |
| commit | e0ccc45b056d626d4b271820faeedf3837337ceb (patch) | |
| tree | b61d89089fe57033cd1e64d51211dcfd6ac7e012 /tools/perf/scripts/python/exported-sql-viewer.py | |
| parent | KVM: arm64: Force HCR_EL2.xMO to 1 at all times in VHE mode (diff) | |
| download | linux-rng-e0ccc45b056d626d4b271820faeedf3837337ceb.tar.xz linux-rng-e0ccc45b056d626d4b271820faeedf3837337ceb.zip | |
KVM: arm64: selftests: Add test for SVE host corruption
Until recently, the kernel could unexpectedly discard SVE state for a
period after a KVM_RUN ioctl, when the guest did not execute any
FPSIMD/SVE/SME instructions. We fixed that issue in commit:
fbc7e61195e2 ("KVM: arm64: Unconditionally save+flush host FPSIMD/SVE/SME state")
Add a test which tries to provoke that issue by manipulating SVE state
before/after running a guest which does not execute any FPSIMD/SVE/SME
instructions. The test executes a handful of iterations to miminize
the risk that the issue is masked by preemption.
Signed-off--by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
Acked-by: Mark Rutland <mark.rutland@arm.com>
Link: https://lore.kernel.org/r/20250417-kvm-selftest-sve-signal-v1-1-6330c2f3da0c@kernel.org
[maz: Restored MR's SoB, fixed commit message according to MR's write-up]
Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions