[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200302195736.24777-1-sean.j.christopherson@intel.com>
Date: Mon, 2 Mar 2020 11:57:30 -0800
From: Sean Christopherson <sean.j.christopherson@...el.com>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: Sean Christopherson <sean.j.christopherson@...el.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Wanpeng Li <wanpengli@...cent.com>,
Jim Mattson <jmattson@...gle.com>,
Joerg Roedel <joro@...tes.org>, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, Jan Kiszka <jan.kiszka@...mens.com>,
Xiaoyao Li <xiaoyao.li@...el.com>
Subject: [PATCH 0/6] KVM: x86: CPUID emulation and tracing fixes
Two fixes related to out-of-range CPUID emulation and related cleanup on
top.
I have a unit test and also manually verified a few interesting cases.
I'm not planning on posting the unit test at this time because I haven't
figured out how to avoid false positives, e.g. if a random in-bounds
leaf just happens to match the output of a max basic leaf. It might be
doable by hardcoding the cpu model?
Sean Christopherson (6):
KVM: x86: Fix tracing of CPUID.function when function is out-of-range
KVM: x86: Fix CPUID range check for Centaur and Hypervisor ranges
KVM: x86: Add dedicated emulator helper for grabbing CPUID.maxphyaddr
KVM: x86: Drop return value from kvm_cpuid()
KVM: x86: Rename "found" variable in kvm_cpuid() to
"exact_entry_exists"
KVM: x86: Add requested index to the CPUID tracepoint
arch/x86/include/asm/kvm_emulate.h | 3 ++-
arch/x86/kvm/cpuid.c | 26 ++++++++++++--------------
arch/x86/kvm/cpuid.h | 2 +-
arch/x86/kvm/emulate.c | 10 +---------
arch/x86/kvm/trace.h | 13 ++++++++-----
arch/x86/kvm/x86.c | 10 ++++++++--
6 files changed, 32 insertions(+), 32 deletions(-)
--
2.24.1
Powered by blists - more mailing lists