From: Greg KH <greg@kroah.com>
To: Kyle Huey <me@kylehuey.com>
Cc: stable@vger.kernel.org, kvm@vger.kernel.org, x86@kernel.org,
Robert O'Callahan <robert@ocallahan.org>,
Keno Fischer <keno@juliacomputing.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 5.4] KVM: x86/svm: Account for family 17h event renumberings in amd_pmc_perf_hw_id
Date: Thu, 12 May 2022 18:22:13 +0200 [thread overview]
Message-ID: <Yn00NbPVMOUF9yM/@kroah.com> (raw)
In-Reply-To: <20220512143852.90281-1-khuey@kylehuey.com>
On Thu, May 12, 2022 at 07:38:52AM -0700, Kyle Huey wrote:
> From: Kyle Huey <me@kylehuey.com>
>
> commit 5eb849322d7f7ae9d5c587c7bc3b4f7c6872cd2f upstream
>
> Zen renumbered some of the performance counters that correspond to the
> well known events in perf_hw_id. This code in KVM was never updated for
> that, so guest that attempt to use counters on Zen that correspond to the
> pre-Zen perf_hw_id values will silently receive the wrong values.
>
> This has been observed in the wild with rr[0] when running in Zen 3
> guests. rr uses the retired conditional branch counter 00d1 which is
> incorrectly recognized by KVM as PERF_COUNT_HW_STALLED_CYCLES_BACKEND.
>
> [0] https://rr-project.org/
>
> Signed-off-by: Kyle Huey <me@kylehuey.com>
> Message-Id: <20220503050136.86298-1-khuey@kylehuey.com>
> Cc: stable@vger.kernel.org
> [Check guest family, not host. - Paolo]
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> [Backport to 5.15: adjusted context]
> Signed-off-by: Kyle Huey <me@kylehuey.com>
> ---
> arch/x86/kvm/pmu_amd.c | 28 +++++++++++++++++++++++++---
> 1 file changed, 25 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/kvm/pmu_amd.c b/arch/x86/kvm/pmu_amd.c
> index f843c6bbcd31..799b9a3144e3 100644
> --- a/arch/x86/kvm/pmu_amd.c
> +++ b/arch/x86/kvm/pmu_amd.c
> @@ -44,6 +44,22 @@ static struct kvm_event_hw_type_mapping amd_event_mapping[] = {
> [7] = { 0xd1, 0x00, PERF_COUNT_HW_STALLED_CYCLES_BACKEND },
> };
>
> +/* duplicated from amd_f17h_perfmon_event_map. */
> +static struct kvm_event_hw_type_mapping amd_f17h_event_mapping[] = {
> + [0] = { 0x76, 0x00, PERF_COUNT_HW_CPU_CYCLES },
> + [1] = { 0xc0, 0x00, PERF_COUNT_HW_INSTRUCTIONS },
> + [2] = { 0x60, 0xff, PERF_COUNT_HW_CACHE_REFERENCES },
> + [3] = { 0x64, 0x09, PERF_COUNT_HW_CACHE_MISSES },
> + [4] = { 0xc2, 0x00, PERF_COUNT_HW_BRANCH_INSTRUCTIONS },
> + [5] = { 0xc3, 0x00, PERF_COUNT_HW_BRANCH_MISSES },
> + [6] = { 0x87, 0x02, PERF_COUNT_HW_STALLED_CYCLES_FRONTEND },
> + [7] = { 0x87, 0x01, PERF_COUNT_HW_STALLED_CYCLES_BACKEND },
> +};
> +
> +/* amd_pmc_perf_hw_id depends on these being the same size */
> +static_assert(ARRAY_SIZE(amd_event_mapping) ==
> + ARRAY_SIZE(amd_f17h_event_mapping));
> +
> static unsigned int get_msr_base(struct kvm_pmu *pmu, enum pmu_type type)
> {
> struct kvm_vcpu *vcpu = pmu_to_vcpu(pmu);
> @@ -128,19 +144,25 @@ static inline struct kvm_pmc *get_gp_pmc_amd(struct kvm_pmu *pmu, u32 msr,
>
> static unsigned int amd_pmc_perf_hw_id(struct kvm_pmc *pmc)
> {
> + struct kvm_event_hw_type_mapping *event_mapping;
> u8 event_select = pmc->eventsel & ARCH_PERFMON_EVENTSEL_EVENT;
> u8 unit_mask = (pmc->eventsel & ARCH_PERFMON_EVENTSEL_UMASK) >> 8;
> int i;
>
> + if (guest_cpuid_family(pmc->vcpu) >= 0x17)
> + event_mapping = amd_f17h_event_mapping;
> + else
> + event_mapping = amd_event_mapping;
> +
> for (i = 0; i < ARRAY_SIZE(amd_event_mapping); i++)
> - if (amd_event_mapping[i].eventsel == event_select
> - && amd_event_mapping[i].unit_mask == unit_mask)
> + if (event_mapping[i].eventsel == event_select
> + && event_mapping[i].unit_mask == unit_mask)
> break;
>
> if (i == ARRAY_SIZE(amd_event_mapping))
> return PERF_COUNT_HW_MAX;
>
> - return amd_event_mapping[i].event_type;
> + return event_mapping[i].event_type;
> }
>
> /* return PERF_COUNT_HW_MAX as AMD doesn't have fixed events */
> --
> 2.36.0
>
Now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2022-05-12 16:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 14:38 [PATCH 5.4] KVM: x86/svm: Account for family 17h event renumberings in amd_pmc_perf_hw_id Kyle Huey
2022-05-12 16:22 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-08 16:54 Kyle Huey
2022-05-09 11:41 ` Paolo Bonzini
2022-05-10 11:33 ` Greg KH
2022-05-10 11:37 ` Greg KH
2022-05-10 11:38 ` Greg KH
2022-05-10 13:11 ` Kyle Huey
2022-05-10 16:01 ` Kyle Huey
2022-05-12 13:48 ` Greg KH
2022-05-12 14:40 ` Kyle Huey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yn00NbPVMOUF9yM/@kroah.com \
--to=greg@kroah.com \
--cc=keno@juliacomputing.com \
--cc=kvm@vger.kernel.org \
--cc=me@kylehuey.com \
--cc=pbonzini@redhat.com \
--cc=robert@ocallahan.org \
--cc=stable@vger.kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox