From: David Dunn <daviddunn@google.com>
To: kvm@vger.kernel.org, pbonzini@redhat.com,
like.xu.linux@gmail.com, jmattson@google.com,
cloudliang@tencent.com, seanjc@google.com
Cc: daviddunn@google.com
Subject: [PATCH v3 0/3] KVM: x86: Provide per VM capability for disabling PMU virtualization
Date: Fri, 21 Jan 2022 21:06:59 +0000 [thread overview]
Message-ID: <20220121210702.635477-1-daviddunn@google.com> (raw)
This patch set allows usermode to disable PMU virtualization on
individual x86 VMs. When disabled, the PMU is not advertised to
or accessible from the guest.
Thanks again to Like and Sean for great feedback. I have incorporated
Like's v2 suggestions in this version.
David Dunn (3):
KVM: x86: Provide per VM capability for disabling PMU virtualization
KVM: selftests: Allow creation of selftest VM without vcpus
KVM: selftests: Verify disabling PMU virtualization via
KVM_CAP_CONFIG_PMU
Documentation/virt/kvm/api.rst | 21 ++++++++
arch/x86/include/asm/kvm_host.h | 1 +
arch/x86/kvm/cpuid.c | 8 ++++
arch/x86/kvm/svm/pmu.c | 2 +-
arch/x86/kvm/vmx/pmu_intel.c | 2 +-
arch/x86/kvm/x86.c | 12 +++++
include/uapi/linux/kvm.h | 4 ++
tools/include/uapi/linux/kvm.h | 4 ++
.../selftests/kvm/include/kvm_util_base.h | 3 ++
tools/testing/selftests/kvm/lib/kvm_util.c | 48 ++++++++++++++-----
.../kvm/x86_64/pmu_event_filter_test.c | 35 ++++++++++++++
11 files changed, 125 insertions(+), 15 deletions(-)
--
2.35.0.rc0.227.g00780c9af4-goog
next reply other threads:[~2022-01-21 21:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 21:06 David Dunn [this message]
2022-01-21 21:07 ` [PATCH v3 1/3] KVM: x86: Provide per VM capability for disabling PMU virtualization David Dunn
2022-01-21 21:07 ` [PATCH v3 2/3] KVM: selftests: Allow creation of selftest VM without vcpus David Dunn
2022-01-21 21:07 ` [PATCH v3 3/3] KVM: selftests: Verify disabling PMU virtualization via KVM_CAP_CONFIG_PMU David Dunn
2022-01-21 22:20 ` [PATCH v3 0/3] KVM: x86: Provide per VM capability for disabling PMU virtualization David Dunn
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=20220121210702.635477-1-daviddunn@google.com \
--to=daviddunn@google.com \
--cc=cloudliang@tencent.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=like.xu.linux@gmail.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.