From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org
Subject: KVM: x86: Second batch of updates for 6.1, i.e. kvm/queue
Date: Wed, 28 Sep 2022 23:56:26 +0000 [thread overview]
Message-ID: <YzTfKh3Sv7RB1abm@google.com> (raw)
Second and likely final batch of x86 updates for 6.1, i.e. for kvm/queue. All
larger series (NX precision, Hyper-V TLB flush, AVIC fixes, etc...) are
destined for 6.2.
There are a variety of selftest fixes and improvements that I think we should
get into 6.1, but they're not x86 specific, i.e. I need to sync with you to
figure out how to handle those.
Note, Like's PEBS KVM-unit-tests[1] will fail unless the PMU fix that's going
through the tip tree is also applied[2]. That's my fault, I requested Like to
post it separately without thinking through the KUT ramifications.
Thanks!
[1] https://lore.kernel.org/all/20220819110939.78013-1-likexu@tencent.com
[2] https://lore.kernel.org/all/20220831033524.58561-1-likexu@tencent.com
The following changes since commit c59fb127583869350256656b7ed848c398bef879:
KVM: remove KVM_REQ_UNHALT (2022-09-26 12:37:21 -0400)
are available in the Git repository at:
https://github.com/sean-jc/linux.git tags/kvm-x86-6.1-2
for you to fetch changes up to ea5cbc9ff839091a86558d4e2c082225b13e0055:
KVM: x86/svm/pmu: Rewrite get_gp_pmc_amd() for more counters scalability (2022-09-28 12:47:23 -0700)
----------------------------------------------------------------
KVM x86 updates for 6.1, batch #2:
- Misc PMU fixes and cleanups.
- Fixes for Hyper-V hypercall selftest
----------------------------------------------------------------
Like Xu (6):
KVM: x86/pmu: Avoid setting BIT_ULL(-1) to pmu->host_cross_mapped_mask
KVM: x86/pmu: Don't generate PEBS records for emulated instructions
KVM: x86/pmu: Refactor PERF_GLOBAL_CTRL update helper for reuse by PEBS
KVM: x86/pmu: Avoid using PEBS perf_events for normal counters
KVM: x86/svm/pmu: Direct access pmu->gp_counter[] to implement amd_*_to_pmc()
KVM: x86/svm/pmu: Rewrite get_gp_pmc_amd() for more counters scalability
Vipin Sharma (2):
KVM: selftests: Check result in hyperv_features for successful hypercalls
KVM: selftests: Load RAX with -EFAULT before Hyper-V hypercall
Vitaly Kuznetsov (1):
KVM: selftests: Don't set reserved bits for invalid Hyper-V hypercall number
arch/x86/kvm/pmu.c | 20 ++++++++++++++-----
arch/x86/kvm/svm/pmu.c | 117 +++++++++++++++++++---------------------------------------------------------------------------------------------
arch/x86/kvm/vmx/pmu_intel.c | 29 +++++++++++++++-------------
tools/testing/selftests/kvm/x86_64/hyperv_features.c | 13 +++++++------
4 files changed, 57 insertions(+), 122 deletions(-)
reply other threads:[~2022-09-28 23:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=YzTfKh3Sv7RB1abm@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.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