diff options
| author | Sean Christopherson <[email protected]> | 2022-06-14 20:06:26 +0000 |
|---|---|---|
| committer | Sean Christopherson <[email protected]> | 2022-07-13 18:14:08 -0700 |
| commit | 4c16fa3ee945183a2f4718a45035e1835c19205b (patch) | |
| tree | 07f7556bf6d978f1c2488a4dda5379eac96c83f5 /tools/perf/scripts/python | |
| parent | 594a1c271c159c9c5f0ff2d92ebfda469e94e48d (diff) | |
KVM: selftests: Set KVM's supported CPUID as vCPU's CPUID during recreate
On x86-64, set KVM's supported CPUID as the vCPU's CPUID when recreating
a VM+vCPU to deduplicate code for state save/restore tests, and to
provide symmetry of sorts with respect to vm_create_with_one_vcpu(). The
extra KVM_SET_CPUID2 call is wasteful for Hyper-V, but ultimately is
nothing more than an expensive nop, and overriding the vCPU's CPUID with
the Hyper-V CPUID information is the only known scenario where a state
save/restore test wouldn't need/want the default CPUID.
Opportunistically use __weak for the default vm_compute_max_gfn(), it's
provided by tools' compiler.h.
Signed-off-by: Sean Christopherson <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions