[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <175798196007.623278.10358907796048599575.b4-ty@google.com>
Date: Mon, 15 Sep 2025 17:25:49 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Sean Christopherson <seanjc@...gle.com>, pbonzini@...hat.com, Yan Zhao <yan.y.zhao@...el.com>
Cc: reinette.chatre@...el.com, rick.p.edgecombe@...el.com,
linux-kernel@...r.kernel.org, kvm@...r.kernel.org
Subject: Re: [PATCH v2 0/3] KVM: Fix deadlock for invalid memslots
On Fri, 22 Aug 2025 15:03:04 +0800, Yan Zhao wrote:
> This series addresses the deadlock issue encountered with invalid memslots
> during prefaulting or TDX private EPT violations.
>
> Patches 1-2 are the new fixes from Sean.
> Patch 1 is for the prefaulting case,
> patch 2 for the TDX private EPT violation case.
>
> [...]
Applied 1 and 2 to kvm-x86 mmu. I'll post a proper patch for the selftest once
I figure out what I intended with respect to range.size.
Thanks!
[1/3] KVM: x86/mmu: Return -EAGAIN if userspace deletes/moves memslot during prefault
https://github.com/kvm-x86/linux/commit/3ccbf6f47098
[2/3] KVM: TDX: Do not retry locally when the retry is caused by invalid memslot
https://github.com/kvm-x86/linux/commit/2bc2694fe20b
--
https://github.com/kvm-x86/linux/tree/next
Powered by blists - more mailing lists