From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Sean Christopherson <seanjc@google.com>
Subject: [GIT PULL] KVM: Fixes for 6.10-rcN
Date: Thu, 20 Jun 2024 16:09:37 -0700 [thread overview]
Message-ID: <20240620230937.2214992-1-seanjc@google.com> (raw)
Two selftests fixes and two KVM fixes for 6.10. Only the kvm_vcpu_on_spin()
fix is tagged for stable@. I deliberately didn't tag the mmu_notifier issue
for stable@ as I'm 99.9% certain it can't actually cause problems (other than
making UBSAN sad).
Sorry for the late-in-the-week request, I have a feeling I missed your window
where you're working on stuff for this week's KVM pull request. :-/
The following changes since commit c3f38fa61af77b49866b006939479069cd451173:
Linux 6.10-rc2 (2024-06-02 15:44:56 -0700)
are available in the Git repository at:
https://github.com/kvm-x86/linux.git tags/kvm-x86-fixes-6.10-rcN
for you to fetch changes up to c3f3edf73a8f854f8766a69d2734198a58762e33:
KVM: Stop processing *all* memslots when "null" mmu_notifier handler is found (2024-06-18 08:51:03 -0700)
----------------------------------------------------------------
KVM fixes for 6.10
- Fix a "shift too big" goof in the KVM_SEV_INIT2 selftest.
- Compute the max mappable gfn for KVM selftests on x86 using GuestMaxPhyAddr
from KVM's supported CPUID (if it's available).
- Fix a race in kvm_vcpu_on_spin() by ensuring loads and stores are atomic.
- Fix technically benign bug in __kvm_handle_hva_range() where KVM consumes
the return from a void-returning function as if it were a boolean.
----------------------------------------------------------------
Babu Moger (1):
KVM: Stop processing *all* memslots when "null" mmu_notifier handler is found
Breno Leitao (1):
KVM: Fix a data race on last_boosted_vcpu in kvm_vcpu_on_spin()
Colin Ian King (1):
KVM: selftests: Fix shift of 32 bit unsigned int more than 32 bits
Tao Su (1):
KVM: selftests: x86: Prioritize getting max_gfn from GuestPhysBits
tools/testing/selftests/kvm/include/x86_64/processor.h | 1 +
tools/testing/selftests/kvm/lib/x86_64/processor.c | 15 +++++++++++++--
tools/testing/selftests/kvm/x86_64/sev_init2_tests.c | 4 ++--
virt/kvm/kvm_main.c | 8 +++++---
4 files changed, 21 insertions(+), 7 deletions(-)
next reply other threads:[~2024-06-20 23:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 23:09 Sean Christopherson [this message]
2024-06-21 12:02 ` 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=20240620230937.2214992-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®