diff options
| author |  Sean Christopherson <seanjc@google.com>
| 2023-11-03 16:05:38 -0700 |
|---|---|---|
| committer | Sean Christopherson <seanjc@google.com>
| 2023-11-30 12:52:54 -0800 |
| commit | f2f63f7ec6fd13d2d5d5c6d90ea438fbb5a36adc (patch) | |
| tree | 2b134778c9d58bc34bde54959ab2c745ead60cdd /arch/x86/kvm/pmu.c | |
| parent | KVM: x86/pmu: Reset the PMU, i.e. stop counters, before refreshing (diff) | |
| download | linux-f2f63f7ec6fd13d2d5d5c6d90ea438fbb5a36adc.tar.gz linux-f2f63f7ec6fd13d2d5d5c6d90ea438fbb5a36adc.tar.bz2 linux-f2f63f7ec6fd13d2d5d5c6d90ea438fbb5a36adc.zip | |
KVM: x86/pmu: Stop calling kvm_pmu_reset() at RESET (it's redundant)
Drop kvm_vcpu_reset()'s call to kvm_pmu_reset(), the call is performed
only for RESET, which is really just the same thing as vCPU creation,
and kvm_arch_vcpu_create() *just* called kvm_pmu_init(), i.e. there can't
possibly be any work to do.
Unlike Intel, AMD's amd_pmu_refresh() does fill all_valid_pmc_idx even if
guest CPUID is empty, but everything that is at all dynamic is guaranteed
to be '0'/NULL, e.g. it should be impossible for KVM to have already
created a perf event.
Reviewed-by: Dapeng Mi <dapeng1.mi@linux.intel.com>
Link: https://lore.kernel.org/r/20231103230541.352265-4-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'arch/x86/kvm/pmu.c')
| -rw-r--r-- | arch/x86/kvm/pmu.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/x86/kvm/pmu.c b/arch/x86/kvm/pmu.c index dc8e8e907cfb..458e836c6efe 100644 --- a/arch/x86/kvm/pmu.c +++ b/arch/x86/kvm/pmu.c @@ -657,7 +657,7 @@ int kvm_pmu_set_msr(struct kvm_vcpu *vcpu, struct msr_data *msr_info) return 0; } -void kvm_pmu_reset(struct kvm_vcpu *vcpu) +static void kvm_pmu_reset(struct kvm_vcpu *vcpu) { struct kvm_pmu *pmu = vcpu_to_pmu(vcpu); struct kvm_pmc *pmc; |