public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Sean Christopherson <seanjc@google.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>,
	Wanpeng Li <wanpengli@tencent.com>,
	Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Like Xu <likexu@tencent.com>
Subject: [PATCH 0/7] KVM: x86: Attempt to wrangle PEBS/PMU into submission
Date: Sat, 11 Jun 2022 00:57:48 +0000	[thread overview]
Message-ID: <20220611005755.753273-1-seanjc@google.com> (raw)

Attempt to fix the myriad PEBS/PMU issues in kvm/next.  Ideally this would
have been code review feedback, but I missed that boat.

Lightly tested, and I haven't thought through the host_initiated stuff too
deeply, but KUT and selftests are happy.

Sean Christopherson (7):
  KVM: x86: Give host userspace full control of MSR_IA32_MISC_ENABLES
  KVM: VMX:  Give host userspace full control of
    MSR_IA32_PERF_CAPABILITIES
  Revert "KVM: x86/pmu: Accept 0 for absent PMU MSRs when host-initiated
    if !enable_pmu"
  Revert "KVM: x86: always allow host-initiated writes to PMU MSRs"
  KVM: VMX: Use vcpu_get_perf_capabilities() to get guest-visible value
  KVM: x86: Ignore benign host accesses to "unsupported" PEBS and BTS
    MSRs
  KVM: x86: Ignore benign host writes to "unsupported" F15H_PERF_CTL
    MSRs

 arch/x86/kvm/pmu.c           | 12 ++------
 arch/x86/kvm/pmu.h           |  4 +--
 arch/x86/kvm/svm/pmu.c       | 13 ++-------
 arch/x86/kvm/vmx/pmu_intel.c | 43 +++++++++++-----------------
 arch/x86/kvm/x86.c           | 55 ++++++++++++++++++++++++------------
 5 files changed, 59 insertions(+), 68 deletions(-)


base-commit: 0cfd9c71371d4c7f96212d20833c36953eccdb91
-- 
2.36.1.476.g0c4daa206d-goog


             reply	other threads:[~2022-06-11  0:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11  0:57 Sean Christopherson [this message]
2022-06-11  0:57 ` [PATCH 1/7] KVM: x86: Give host userspace full control of MSR_IA32_MISC_ENABLES Sean Christopherson
2022-06-11  0:57 ` [PATCH 2/7] KVM: VMX: Give host userspace full control of MSR_IA32_PERF_CAPABILITIES Sean Christopherson
2022-06-11  0:57 ` [PATCH 3/7] Revert "KVM: x86/pmu: Accept 0 for absent PMU MSRs when host-initiated if !enable_pmu" Sean Christopherson
2022-06-11  0:57 ` [PATCH 4/7] Revert "KVM: x86: always allow host-initiated writes to PMU MSRs" Sean Christopherson
2022-06-11  0:57 ` [PATCH 5/7] KVM: VMX: Use vcpu_get_perf_capabilities() to get guest-visible value Sean Christopherson
2022-06-11  0:57 ` [PATCH 6/7] KVM: x86: Ignore benign host accesses to "unsupported" PEBS and BTS MSRs Sean Christopherson
2022-06-13 14:09   ` Sean Christopherson
2022-06-20 14:29     ` Paolo Bonzini
2022-06-14  7:45   ` Vitaly Kuznetsov
2022-06-11  0:57 ` [PATCH 7/7] KVM: x86: Ignore benign host writes to "unsupported" F15H_PERF_CTL MSRs Sean Christopherson
2022-06-20 14:31 ` [PATCH 0/7] KVM: x86: Attempt to wrangle PEBS/PMU into submission 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=20220611005755.753273-1-seanjc@google.com \
    --to=seanjc@google.com \
    --cc=jmattson@google.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=likexu@tencent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=vkuznets@redhat.com \
    --cc=wanpengli@tencent.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