diff options
| author | Sean Christopherson <[email protected]> | 2023-06-13 20:30:37 +0000 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2023-07-29 15:05:32 +0000 |
| commit | 5a7591176c47cce363c1eed704241e5d1c42c5a6 (patch) | |
| tree | ab592ba4cf60a9185dd31a08c039c3e3a0ec0b31 /tools/perf/builtin-script.c | |
| parent | KVM: VMX: Don't fudge CR0 and CR4 for restricted L2 guest (diff) | |
| download | kernel-5a7591176c47cce363c1eed704241e5d1c42c5a6.tar.gz kernel-5a7591176c47cce363c1eed704241e5d1c42c5a6.zip | |
KVM: selftests: Expand x86's sregs test to cover illegal CR0 values
Add coverage to x86's set_sregs_test to verify KVM rejects vendor-agnostic
illegal CR0 values, i.e. CR0 values whose legality doesn't depend on the
current VMX mode. KVM historically has neglected to reject bad CR0s from
userspace, i.e. would happily accept a completely bogus CR0 via
KVM_SET_SREGS{2}.
Punt VMX specific subtests to future work, as they would require quite a
bit more effort, and KVM gets coverage for CR0 checks in general through
other means, e.g. KVM-Unit-Tests.
Signed-off-by: Sean Christopherson <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'tools/perf/builtin-script.c')
0 files changed, 0 insertions, 0 deletions