[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1e0fc70a-1135-1845-b534-79f409e0c29d@gmail.com>
Date: Mon, 21 Feb 2022 15:57:05 +0800
From: Like Xu <like.xu.linux@...il.com>
To: Ravi Bangoria <ravi.bangoria@....com>
Cc: seanjc@...gle.com, jmattson@...gle.com,
dave.hansen@...ux.intel.com, peterz@...radead.org,
alexander.shishkin@...ux.intel.com, eranian@...gle.com,
daviddunn@...gle.com, ak@...ux.intel.com,
kan.liang@...ux.intel.com, x86@...nel.org, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, kim.phillips@....com,
santosh.shukla@....com,
"Paolo Bonzini - Distinguished Engineer (kernel-recipes.org) (KVM HoF)"
<pbonzini@...hat.com>
Subject: Re: [PATCH 3/3] KVM: x86/pmu: Segregate Intel and AMD specific logic
On 21/2/2022 3:31 pm, Ravi Bangoria wrote:
> void reprogram_counter(struct kvm_pmu *pmu, int pmc_idx)
> {
> struct kvm_pmc *pmc = kvm_x86_ops.pmu_ops->pmc_idx_to_pmc(pmu, pmc_idx);
> + bool is_intel = !strncmp(kvm_x86_ops.name, "kvm_intel", 9);
How about using guest_cpuid_is_intel(vcpu) directly in the reprogram_gp_counter() ?
Powered by blists - more mailing lists