diff options
| author | Sean Christopherson <sean.j.christopherson@intel.com> | 2020-03-17 12:53:54 -0700 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2020-03-18 13:44:43 +0100 |
| commit | 2b110b61644a34e97c92ae20788cbcb42d474fa9 (patch) | |
| tree | dfdfd6626cd1d4626423f8c8065bb9ebbad1c620 /tools/testing/selftests/kvm/lib/test_util.c | |
| parent | e7adda281063becab7631c6ac60f8b19684ba042 (diff) | |
| download | linux-2b110b61644a34e97c92ae20788cbcb42d474fa9.tar.bz2 | |
KVM: x86: Add blurb to CPUID tracepoint when using max basic leaf values
Tack on "used max basic" at the end of the CPUID tracepoint when the
output values correspond to the max basic leaf, i.e. when emulating
Intel's out-of-range CPUID behavior. Observing "cpuid entry not found"
in the tracepoint with non-zero output values is confusing for users
that aren't familiar with the out-of-range semantics, and qualifying the
"not found" case hopefully makes it clear that "found" means "found the
exact entry".
Suggested-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/testing/selftests/kvm/lib/test_util.c')
0 files changed, 0 insertions, 0 deletions