Sean Christopherson 5a7591176c 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>		2023-07-29 11:05:32 -04:00
..
crypto/chacha20-s390
cxl	Merge branch 'for-6.5/cxl-rch-eh' into for-6.5/cxl	2023-06-25 18:56:13 -07:00
fault-injection
ktest	ktest: Restore stty setting at first in dodie	2023-02-20 11:52:27 -05:00
kunit	hardening updates for v6.5-rc1	2023-06-27 21:24:18 -07:00
memblock	Add tests for memblock_alloc_node()	2023-05-24 11:56:30 +03:00
nvdimm	tools/testing/nvdimm: Drop empty platform remove function	2023-06-07 13:30:21 -07:00
radix-tree	maple_tree: fix node allocation testing on 32 bit	2023-07-17 12:53:22 -07:00
scatterlist
selftests	KVM: selftests: Expand x86's sregs test to cover illegal CR0 values	2023-07-29 11:05:32 -04:00
vsock	vsock/test: update expected return values	2023-04-04 12:46:24 +02:00