diff options
| author | Sean Christopherson <[email protected]> | 2024-11-28 00:55:44 +0000 |
|---|---|---|
| committer | Sean Christopherson <[email protected]> | 2024-12-18 22:15:02 +0000 |
| commit | b6c304aec6483f6cd254df690eda35b225cd856c (patch) | |
| tree | 388c6e01da5e51b48d4ef3702c60ee647ef56e05 /tools/testing/selftests/kvm/x86/hyperv_evmcs.c | |
| parent | KVM: selftests: Add a read-only mprotect() phase to mmu_stress_test (diff) | |
| download | kernel-b6c304aec6483f6cd254df690eda35b225cd856c.tar.gz kernel-b6c304aec6483f6cd254df690eda35b225cd856c.zip | |
KVM: selftests: Verify KVM correctly handles mprotect(PROT_READ)
Add two phases to mmu_stress_test to verify that KVM correctly handles
guest memory that was writable, and then made read-only in the primary MMU,
and then made writable again.
Add bonus coverage for x86 and arm64 to verify that all of guest memory was
marked read-only. Making forward progress (without making memory writable)
requires arch specific code to skip over the faulting instruction, but the
test can at least verify each vCPU's starting page was made read-only for
other architectures.
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Sean Christopherson <[email protected]>
Diffstat (limited to 'tools/testing/selftests/kvm/x86/hyperv_evmcs.c')
0 files changed, 0 insertions, 0 deletions