aboutsummaryrefslogtreecommitdiff
path: root/tools/testing/selftests/kvm/set_memory_region_test.c
diff options
context:
space:
mode:
authorAndrew Jones <drjones@redhat.com>2020-11-11 13:26:35 +0100
committerPaolo Bonzini <pbonzini@redhat.com>2020-11-16 13:14:20 -0500
commit22f232d134e142022f5e4cf2de4587a34d5b7d65 (patch)
tree627ac0a9404820636fe21beed6ac35ca8041e175 /tools/testing/selftests/kvm/set_memory_region_test.c
parent08d3e27718bd45ea3284b1b99a2082a233b8667c (diff)
KVM: selftests: x86: Set supported CPUIDs on default VM
Almost all tests do this anyway and the ones that don't don't appear to care. Only vmx_set_nested_state_test assumes that a feature (VMX) is disabled until later setting the supported CPUIDs. It's better to disable that explicitly anyway. Signed-off-by: Andrew Jones <drjones@redhat.com> Message-Id: <20201111122636.73346-11-drjones@redhat.com> [Restore CPUID_VMX, or vmx_set_nested_state breaks. - Paolo] Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/testing/selftests/kvm/set_memory_region_test.c')
-rw-r--r--tools/testing/selftests/kvm/set_memory_region_test.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/tools/testing/selftests/kvm/set_memory_region_test.c b/tools/testing/selftests/kvm/set_memory_region_test.c
index b3ece55a2da6..5fa5823661da 100644
--- a/tools/testing/selftests/kvm/set_memory_region_test.c
+++ b/tools/testing/selftests/kvm/set_memory_region_test.c
@@ -121,8 +121,6 @@ static struct kvm_vm *spawn_vm(pthread_t *vcpu_thread, void *guest_code)
vm = vm_create_default(VCPU_ID, 0, guest_code);
- vcpu_set_cpuid(vm, VCPU_ID, kvm_get_supported_cpuid());
-
vm_userspace_mem_region_add(vm, VM_MEM_SRC_ANONYMOUS_THP,
MEM_REGION_GPA, MEM_REGION_SLOT,
MEM_REGION_SIZE / getpagesize(), 0);