From: Binbin Wu <binbin.wu@linux.intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Yan Zhao <yan.y.zhao@intel.com>,
pbonzini@redhat.com, reinette.chatre@intel.com,
rick.p.edgecombe@intel.com, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org
Subject: Re: [PATCH v2 2/3] KVM: TDX: Do not retry locally when the retry is caused by invalid memslot
Date: Wed, 10 Sep 2025 10:02:59 +0800 [thread overview]
Message-ID: <9fa411a9-08d2-44fa-8ef8-18d3f2c8acad@linux.intel.com> (raw)
In-Reply-To: <aMA3LjGP9nezNM7e@google.com>
On 9/9/2025 10:18 PM, Sean Christopherson wrote:
> On Tue, Sep 09, 2025, Binbin Wu wrote:
>> On 8/22/2025 3:05 PM, Yan Zhao wrote:
>>> diff --git a/arch/x86/kvm/vmx/tdx.c b/arch/x86/kvm/vmx/tdx.c
>>> index 6784aaaced87..de2c4bb36069 100644
>>> --- a/arch/x86/kvm/vmx/tdx.c
>>> +++ b/arch/x86/kvm/vmx/tdx.c
>>> @@ -1992,6 +1992,11 @@ static int tdx_handle_ept_violation(struct kvm_vcpu *vcpu)
>>> * blocked by TDs, false positives are inevitable i.e., KVM may re-enter
>>> * the guest even if the IRQ/NMI can't be delivered.
>>> *
>>> + * Breaking out of the local retries if a retry is caused by faulting
>>> + * in an invalid memslot (indicating the slot is under removal), so that
>>> + * the slot removal will not be blocked due to waiting for releasing
>>> + * SRCU lock in the VMExit handler.
>>> + *
>>> * Note: even without breaking out of local retries, zero-step
>>> * mitigation may still occur due to
>>> * - invoking of TDH.VP.ENTER after KVM_EXIT_MEMORY_FAULT,
>>> @@ -2002,6 +2007,8 @@ static int tdx_handle_ept_violation(struct kvm_vcpu *vcpu)
>>> * handle retries locally in their EPT violation handlers.
>>> */
>>> while (1) {
>>> + struct kvm_memory_slot *slot;
>>> +
>>> ret = __vmx_handle_ept_violation(vcpu, gpa, exit_qual);
>>> if (ret != RET_PF_RETRY || !local_retry)
>>> @@ -2015,6 +2022,10 @@ static int tdx_handle_ept_violation(struct kvm_vcpu *vcpu)
>>> break;
>>> }
>>> + slot = kvm_vcpu_gfn_to_memslot(vcpu, gpa_to_gfn(gpa));
>>> + if (slot && slot->flags & KVM_MEMSLOT_INVALID)
>> The slot couldn't be NULL here, right?
> Uh, hmm. It could be NULL. If the memslot deletion starts concurrently with the
> S-EPT violation, then the memslot could be transitioned to INVALID (prepared for
> deletion) prior to the vCPU acquiring SRCU after the VM-Exit. Memslot deletion
> could then assign to kvm->memslots with a NULL memslot.
>
> vCPU DELETE
> S-EPT Violation
> Set KVM_MEMSLOT_INVALID
> synchronize_srcu_expedited()
> Acquire SRCU
> __vmx_handle_ept_violation()
> RET_PF_RETRY due to INVALID
> Set memslot NULL
> kvm_vcpu_gfn_to_memslot()
Got it, thanks!
next prev parent reply other threads:[~2025-09-10 2:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 7:03 [PATCH v2 0/3] KVM: Fix deadlock for invalid memslots Yan Zhao
2025-08-22 7:03 ` [PATCH v2 1/3] KVM: x86/mmu: Return -EAGAIN if userspace deletes/moves memslot during prefault Yan Zhao
2025-09-09 2:46 ` Binbin Wu
2025-08-22 7:05 ` [PATCH v2 2/3] KVM: TDX: Do not retry locally when the retry is caused by invalid memslot Yan Zhao
2025-09-09 3:29 ` Binbin Wu
2025-09-09 14:18 ` Sean Christopherson
2025-09-10 2:02 ` Binbin Wu [this message]
2025-08-22 7:05 ` [PATCH v2 3/3] KVM: selftests: Test prefault memory during concurrent memslot removal Yan Zhao
2025-09-08 23:47 ` Sean Christopherson
2025-09-15 8:21 ` Yan Zhao
2025-09-16 0:14 ` Sean Christopherson
2025-09-24 17:09 ` Sean Christopherson
2025-09-16 0:25 ` [PATCH v2 0/3] KVM: Fix deadlock for invalid memslots 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=9fa411a9-08d2-44fa-8ef8-18d3f2c8acad@linux.intel.com \
--to=binbin.wu@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=yan.y.zhao@intel.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;
as well as URLs for NNTP newsgroup(s).