mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Yan Zhao <yan.y.zhao@intel.com>
Subject: Re: [PATCH v3] KVM: selftests: Test prefault memory during concurrent memslot removal
Date: Fri, 10 Oct 2025 14:30:36 -0700	[thread overview]
Message-ID: <176013138845.972857.17974431872471984207.b4-ty@google.com> (raw)
In-Reply-To: <20250924174255.2141847-1-seanjc@google.com>

On Wed, 24 Sep 2025 10:42:55 -0700, Sean Christopherson wrote:
> Expand the prefault memory selftest to add a regression test for a KVM bug
> where TDX's retry logic (to avoid tripping the zero-step mitigation) would
> result in deadlock due to the memslot deletion waiting on prefaulting to
> release SRCU, and prefaulting waiting on the memslot to fully disappear
> (KVM uses a two-step process to delete memslots, and KVM x86 retries page
> faults if a to-be-deleted, a.k.a. INVALID, memslot is encountered).
> 
> [...]

Applied to kvm-x86 fixes, with a massaged changelog to call out that it's
KVM's retry logic, not the TDX-specific zero-step logic that is being tested.

[1/1] KVM: selftests: Test prefault memory during concurrent memslot removal
      https://github.com/kvm-x86/linux/commit/1bcc3f879127

--
https://github.com/kvm-x86/linux/tree/next

      parent reply	other threads:[~2025-10-10 21:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-24 17:42 Sean Christopherson
2025-09-26  3:08 ` Yan Zhao
2025-09-26  7:59   ` Yan Zhao
2025-10-10 21:30 ` Sean Christopherson [this message]

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=176013138845.972857.17974431872471984207.b4-ty@google.com \
    --to=seanjc@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.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

all inboxes | Powered by JetHome®