KVM: selftests: Expand x86's sregs test to cover illegal CR0 values
authorSean Christopherson <seanjc@google.com>
Tue, 13 Jun 2023 20:30:37 +0000 (13:30 -0700)
committerPaolo Bonzini <pbonzini@redhat.com>
Sat, 29 Jul 2023 15:05:32 +0000 (11:05 -0400)
commit5a7591176c47cce363c1eed704241e5d1c42c5a6
treeab592ba4cf60a9185dd31a08c039c3e3a0ec0b31
parentc4abd7352023aa96114915a0bb2b88016a425cda
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 <seanjc@google.com>
Message-Id: <20230613203037.1968489-4-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
tools/testing/selftests/kvm/x86_64/set_sregs_test.c