Round two of trying to wrangle kvm_cpuid() into submission. Two more bug
fixes, both related to querying for an "AMD" vendor, in addition to the
fixes in v1 (tracing and Hypervisor/Centaur range checks).
In theory, everything up to the refactoring is non-controversial, i.e. we
can bikeshed the refactoring without delaying the bug fixes.
v2:
- Use Jan's patch to fix the trace bug. [Everyone]
- Rework Hypervisor/Centaur handling so that only the Hypervisor
sub-ranges get the restrictive 0xffffff00 mask, and so that Centaur's
range only gets recognized when the guest vendor is Centaur. [Jim]
- Add the aforementioned bug fixes.
- Add a patch to do build time assertions on the vendor string, which
are hand coded u32s in the emulator (for direct comparison against
CPUID register output).
- Drop the patch to add CPUID.maxphyaddr emulator helper. [Paolo]
- Redo refactoring patches to land them after all the bug fixes
and to do the refactoring without any semantic changes in the
emulator.
Jan Kiszka (1):
KVM: x86: Trace the original requested CPUID function in kvm_cpuid()
Sean Christopherson (6):
KVM: x86: Add helpers to perform CPUID-based guest vendor check
KVM x86: Extend AMD specific guest behavior to Hygon virtual CPUs
KVM: x86: Fix CPUID range checks for Hypervisor and Centaur classes
KVM: x86: Add build-time assertions on validity of vendor strings
KVM: x86: Refactor out-of-range logic to contain the madness
KVM: x86: Refactor kvm_cpuid() param that controls out-of-range logic
arch/x86/include/asm/kvm_emulate.h | 37 +++++++++-
arch/x86/kvm/cpuid.c | 111 +++++++++++++++++++++--------
arch/x86/kvm/cpuid.h | 8 ++-
arch/x86/kvm/emulate.c | 64 ++++++++---------
arch/x86/kvm/mmu/mmu.c | 3 +-
arch/x86/kvm/svm.c | 2 +-
arch/x86/kvm/x86.c | 7 +-
7 files changed, 162 insertions(+), 70 deletions(-)
--
2.24.1
