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: x86: MMU changes for 6.18
Date: Fri, 26 Sep 2025 23:09:03 -0700 [thread overview]
Message-ID: <20250927060910.2933942-4-seanjc@google.com> (raw)
In-Reply-To: <20250927060910.2933942-1-seanjc@google.com>
Recover TDP MMU NX huge pages under read lock, and fix two (interruptible)
deadlocks in prefaulting and in the TDX anti-zero-step code (there's a
selftest from Yan for the prefaulting case that I'll send along later).
The following changes since commit c17b750b3ad9f45f2b6f7e6f7f4679844244f0b9:
Linux 6.17-rc2 (2025-08-17 15:22:10 -0700)
are available in the Git repository at:
https://github.com/kvm-x86/linux.git tags/kvm-x86-mmu-6.18
for you to fetch changes up to 2bc2694fe20bf06eb73524426e3f4581d7b28923:
KVM: TDX: Do not retry locally when the retry is caused by invalid memslot (2025-09-10 12:06:35 -0700)
----------------------------------------------------------------
KVM x86 MMU changes for 6.18
- Recover possible NX huge pages within the TDP MMU under read lock to
reduce guest jitter when restoring NX huge pages.
- Return -EAGAIN during prefault if userspace concurrently deletes/moves the
relevant memslot to fix an issue where prefaulting could deadlock with the
memslot update.
- Don't retry in TDX's anti-zero-step mitigation if the target memslot is
invalid, i.e. is being deleted or moved, to fix a deadlock scenario similar
to the aforementioned prefaulting case.
----------------------------------------------------------------
Sean Christopherson (2):
KVM: x86/mmu: Return -EAGAIN if userspace deletes/moves memslot during prefault
KVM: TDX: Do not retry locally when the retry is caused by invalid memslot
Vipin Sharma (3):
KVM: x86/mmu: Track possible NX huge pages separately for TDP vs. Shadow MMU
KVM: x86/mmu: Rename kvm_tdp_mmu_zap_sp() to better indicate its purpose
KVM: x86/mmu: Recover TDP MMU NX huge pages using MMU read lock
arch/x86/include/asm/kvm_host.h | 39 ++++++----
arch/x86/kvm/mmu/mmu.c | 165 ++++++++++++++++++++++++++--------------
arch/x86/kvm/mmu/mmu_internal.h | 6 +-
arch/x86/kvm/mmu/tdp_mmu.c | 49 +++++++++---
arch/x86/kvm/mmu/tdp_mmu.h | 3 +-
arch/x86/kvm/vmx/tdx.c | 11 +++
virt/kvm/kvm_main.c | 1 +
7 files changed, 192 insertions(+), 82 deletions(-)
next prev parent reply other threads:[~2025-09-27 6:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-27 6:09 [GIT PULL] KVM: x86 pull requests 6.18 Sean Christopherson
2025-09-27 6:09 ` [GIT PULL] x86/kvm: Guest side changes for 6.18 Sean Christopherson
2025-09-30 17:28 ` Paolo Bonzini
2025-09-27 6:09 ` [GIT PULL] KVM: One lone common change " Sean Christopherson
2025-09-30 17:28 ` Paolo Bonzini
2025-09-27 6:09 ` Sean Christopherson [this message]
2025-09-30 17:33 ` [GIT PULL] KVM: x86: MMU changes " Paolo Bonzini
2025-09-27 6:09 ` [GIT PULL] KVM: Selftests " Sean Christopherson
2025-09-30 17:24 ` Paolo Bonzini
2025-09-27 6:09 ` [GIT PULL] KVM: x86: VMX " Sean Christopherson
2025-09-30 17:33 ` Paolo Bonzini
2025-09-27 6:09 ` [GIT PULL] KVM: x86: SVM " Sean Christopherson
2025-09-30 17:35 ` Paolo Bonzini
2025-09-27 6:09 ` [GIT PULL] KVM: x86: SNP CipherTextHiding " Sean Christopherson
2025-09-30 17:35 ` Paolo Bonzini
2025-09-27 6:09 ` [GIT PULL] KVM: x86: Misc changes " Sean Christopherson
2025-09-30 18:06 ` Paolo Bonzini
2025-09-27 6:09 ` [GIT PULL] KVM: x86: CET virtualization " Sean Christopherson
2025-09-27 6:09 ` [GIT PULL] KVM: Symbol export restrictions " Sean Christopherson
2025-09-30 17:41 ` Paolo Bonzini
2025-09-30 18:10 ` [GIT PULL] KVM: x86 pull requests 6.18 Paolo Bonzini
2025-09-30 19:16 ` Sean Christopherson
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=20250927060910.2933942-4-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