summaryrefslogtreecommitdiffstats
path: root/arch/x86/kvm/x86.h
diff options
context:
space:
mode:
authorSean Christopherson <seanjc@google.com>2023-01-24 23:49:00 +0000
committerSean Christopherson <seanjc@google.com>2023-01-26 18:03:42 -0800
commit8911ce66697e04ce7e92753dbf5645f748e27e12 (patch)
treee34fece68393ccf1c987390adc3d9488c7dfe4f8 /arch/x86/kvm/x86.h
parent2a3003e9507c0315e0642247230899485c488ff8 (diff)
downloadlinux-stable-8911ce66697e04ce7e92753dbf5645f748e27e12.tar.gz
linux-stable-8911ce66697e04ce7e92753dbf5645f748e27e12.tar.bz2
linux-stable-8911ce66697e04ce7e92753dbf5645f748e27e12.zip
KVM: x86/pmu: Cap kvm_pmu_cap.num_counters_gp at KVM's internal max
Limit kvm_pmu_cap.num_counters_gp during kvm_init_pmu_capability() based on the vendor PMU capabilities so that consuming num_counters_gp naturally does the right thing. This fixes a mostly theoretical bug where KVM could over-report its PMU support in KVM_GET_SUPPORTED_CPUID for leaf 0xA, e.g. if the number of counters reported by perf is greater than KVM's hardcoded internal limit. Incorporating input from the AMD PMU also avoids over-reporting MSRs to save when running on AMD. Link: https://lore.kernel.org/r/20230124234905.3774678-2-seanjc@google.com Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'arch/x86/kvm/x86.h')
0 files changed, 0 insertions, 0 deletions