From: Paolo Bonzini <pbonzini@redhat.com>
To: Mingwei Zhang <mizhang@google.com>,
Sean Christopherson <seanjc@google.com>,
Frederick Mayle <fmayle@google.com>,
Steven Moreland <smoreland@google.com>
Cc: Aaron Lewis <aaronlewis@google.com>,
"H. Peter Anvin" <hpa@zytor.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] KVM: x86/pmu: Reset perf_capabilities in vcpu to 0 if PDCM is disabled
Date: Mon, 29 Jan 2024 15:40:28 +0100 [thread overview]
Message-ID: <287ec316-1de5-4777-b56a-2a1b22fbe89c@redhat.com> (raw)
In-Reply-To: <CAL715WKMpui=+U56Qc5AiuLhUw_g-bjvtN5OmVz_hGdJmF1M5g@mail.gmail.com>
On 1/26/24 20:30, Mingwei Zhang wrote:
>> Hrm, I don't hate it as a stopgap. But if we are the only people that are affected,
>> because again I'm pretty sure QEMU is fine, I would rather we just fix things in
>> our VMM and/or internal kernel.
> It is not just QEMU. crossvm is another open source VMM that suffers
> from this one.
Can you explain the symptoms in both Google's internal VMM and crosvm?
Thanks,
Paolo
next prev parent reply other threads:[~2024-01-29 14:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 0:38 [PATCH 0/2] minor fix on perf_capabilities in KVM/x86 Mingwei Zhang
2024-01-24 0:38 ` [PATCH 1/2] KVM: x86/pmu: Reset perf_capabilities in vcpu to 0 if PDCM is disabled Mingwei Zhang
2024-01-24 15:49 ` Sean Christopherson
2024-01-24 21:04 ` Aaron Lewis
2024-01-24 21:25 ` Sean Christopherson
2024-01-24 22:24 ` Mingwei Zhang
2024-01-24 22:51 ` Sean Christopherson
2024-01-25 0:14 ` Mingwei Zhang
2024-01-26 18:33 ` Sean Christopherson
2024-01-26 19:30 ` Mingwei Zhang
2024-01-26 19:34 ` Sean Christopherson
2024-01-29 14:40 ` Paolo Bonzini [this message]
2024-01-29 14:39 ` Paolo Bonzini
2024-01-31 19:43 ` Mingwei Zhang
2024-01-24 0:38 ` [PATCH 2/2] KVM: x86/pmu: Remove vcpu_get_perf_capabilities() Mingwei Zhang
2024-01-24 15:52 ` Sean Christopherson
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=287ec316-1de5-4777-b56a-2a1b22fbe89c@redhat.com \
--to=pbonzini@redhat.com \
--cc=aaronlewis@google.com \
--cc=fmayle@google.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mizhang@google.com \
--cc=seanjc@google.com \
--cc=smoreland@google.com \
/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
all inboxes | Powered by JetHome®