From: Sean Christopherson <seanjc@google.com>
To: Jari Ruusu <jariruusu@protonmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] kvm ignores ignore_msrs=1 VETO for some MSRs
Date: Tue, 5 Sep 2023 13:55:48 -0700 [thread overview]
Message-ID: <ZPeV1GWQWeH48a2G@google.com> (raw)
In-Reply-To: <DSxaeYtslZW13dZU36PVY2RooaqU99qcXgPSYkyw6F5t8LSJk8MkAn1shTVrb-cAFRaKEVr5VDrWD6JRmSTlpDbGrHBiM-8zHwIiH90nNHI=@protonmail.com>
On Tue, Sep 05, 2023, Jari Ruusu wrote:
> On Tuesday, September 5th, 2023 at 22:27, Sean Christopherson <seanjc@google.com> wrote:
> > As for working around this in your setup, assuming you don't actually need a
> > virtual PMU in the guest, the simplest workaround would be to turn off vPMU
> > support in KVM, i.e. boot with kvm.enable_pmu=0. That should cause QEMU to not
> > advertise a PMU to the guest.
>
> Newer host kernels seem to have kvm.enable_pmu parameter,
> but linux-5.10.y kernels do not have that.
Gah, try kvm.pmu.
Commit 4732f2444acd ("KVM: x86: Making the module parameter of vPMU more common")
renamed the variable to avoid collisions, but it unnecessarily changed the name
exposed to userspace too. My gut reaction is to revert the param name back to
"pmu".
Paolo, any idea if reverting "enable_pmu" back to "pmu" would be worth the churn?
next prev parent reply other threads:[~2023-09-05 20:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 18:07 [PATCH] kvm ignores ignore_msrs=1 VETO for some MSRs Jari Ruusu
2023-09-05 19:27 ` Sean Christopherson
2023-09-05 20:41 ` Jari Ruusu
2023-09-05 20:55 ` Sean Christopherson [this message]
2023-09-05 21:02 ` Jari Ruusu
2023-09-07 10:55 ` Paolo Bonzini
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=ZPeV1GWQWeH48a2G@google.com \
--to=seanjc@google.com \
--cc=jariruusu@protonmail.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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