Thread (66 messages) 66 messages, 5 authors, 2025-11-10

Re: [PATCH v4 00/28] KVM: x86/mmu: TDX post-populate cleanups

From: Huang, Kai <hidden>
Date: 2025-10-30 23:19:51
Also in: kvm, kvm-riscv, kvmarm, linux-arm-kernel, linux-coco, linux-mips, linux-riscv, lkml, loongarch

On Thu, 2025-10-30 at 13:09 -0700, Sean Christopherson wrote:
Non-x86 folks, as with v3, patches 1 and 2 are likely the only thing of
interest here.  They make kvm_arch_vcpu_async_ioctl() mandatory and then
rename it to kvm_arch_vcpu_unlocked_ioctl().

As for the x86 side...

Clean up the TDX post-populate paths (and many tangentially related paths) to
address locking issues between gmem and TDX's post-populate hook[*], and
within KVM itself (KVM doesn't ensure full mutual exclusivity between paths
that for all intents and purposes the TDX-Module requires to be serialized).
I pulled this series to local, applied to kvm-x86/next and sanity tested
that booting/destroying two TDs worked fine, so:

Tested-by: Kai Huang <redacted>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help