Skip to contentSkip to conversation

KVM: TDX: Decrease TDX VM shutdown time

PATCH Superseded Adrian Hunter 2 participants 5 messages Apr 25, 2025 – Jun 6, 2025

Subsystems (5)
Documentation x86 KVM KVM x86 +1 more subsystems

v3 of 4 Superseded Latest is v4 →

lore
Share & tools
lore
#0 lore raw

v3 cover KVM: TDX: Decrease TDX VM shutdown time

Hi

Changes in V3:
Refer:
https://lore.kernel.org/r/[email protected]

Remove KVM_BUG_ON() from tdx_mmu_release_hkid() because it would trigger on the error path from __tdx_td_init()

Put cpus_read_lock() handling back into tdx_mmu_release_hkid()

Handle KVM_TDX_TERMINATE_VM in the switch statement, i.e. let tdx_vm_ioctl() deal with kvm->lock

The version 1 RFC:

	https://lore.kernel.org/all/[email protected]/

listed 3 options and implemented option 2. Sean replied with code for option 1, which tested out OK, so here it is plus a commit log.

It depends upon kvm_trylock_all_vcpus(kvm) which is the assumed result of Maxim's work-in-progress here:

      https://lore.kernel.org/all/[email protected]/

Note it is assumed that kvm_trylock_all_vcpus(kvm) follows the return value semantics of mutex_trylock() i.e. 1 means locks have been successfully acquired, 0 means not succesful.

Sean Christopherson (1):
KVM: TDX: Add sub-ioctl KVM_TDX_TERMINATE_VM

 Documentation/virt/kvm/x86/intel-tdx.rst | 16 ++++++++
 arch/x86/include/uapi/asm/kvm.h          |  1 +
 arch/x86/kvm/vmx/tdx.c                   | 63 ++++++++++++++++++++++----------
 3 files changed, 61 insertions(+), 19 deletions(-)

Regards
Adrian

#1 lore raw

PATCH v3 1/1 KVM: TDX: Add sub-ioctl KVM_TDX_TERMINATE_VM

From: Sean Christopherson <[email protected]>

Add sub-ioctl KVM_TDX_TERMINATE_VM to release the HKID prior to shutdown, which enables more efficient reclaim of private memory.

Private memory is removed from MMU/TDP when guest_memfds are closed. If the HKID has not been released, the TDX VM is still in RUNNABLE state, so pages must be removed using "Dynamic Page Removal" procedure (refer TDX Module Base spec) which involves a number of steps:
Block further address translation
Exit each VCPU
Clear Secure EPT entry
Flush/write-back/invalidate relevant caches

However, when the HKID is released, the TDX VM moves to TD_TEARDOWN state where all TDX VM pages are effectively unmapped, so pages can be reclaimed directly.

Reclaiming TD Pages in TD_TEARDOWN State was seen to decrease the total reclaim time. For example:

	VCPUs	Size (GB)	Before (secs)	After (secs)
	 4	 18		  72		 24
	32	107		 517		134
	64	400		5539		467

---

Changes in V3:

Remove KVM_BUG_ON() from tdx_mmu_release_hkid() because it would trigger on the error path from __tdx_td_init()

Put cpus_read_lock() handling back into tdx_mmu_release_hkid()

Handle KVM_TDX_TERMINATE_VM in the switch statement, i.e. let tdx_vm_ioctl() deal with kvm->lock

 Documentation/virt/kvm/x86/intel-tdx.rst | 16 +++++++++
 arch/x86/include/uapi/asm/kvm.h          |  1 +
 arch/x86/kvm/vmx/tdx.c                   | 41 +++++++++++++++---------
 3 files changed, 43 insertions(+), 15 deletions(-)
Documentation/virt/kvm/x86/intel-tdx.rst +16 -0
index de41d4c01e5c..e5d4d9cf4cf2 100644
@@ -38,6 +38,7 @@ ioctl with TDX specific sub-ioctl() commands.
           KVM_TDX_INIT_MEM_REGION,
           KVM_TDX_FINALIZE_VM,
           KVM_TDX_GET_CPUID,
+          KVM_TDX_TERMINATE_VM,
 
           KVM_TDX_CMD_NR_MAX,
   };
@@ -214,6 +215,21 @@ struct kvm_cpuid2.
 	  __u32 padding[3];
   };
 
+KVM_TDX_TERMINATE_VM
+-------------------
+:Type: vm ioctl
+:Returns: 0 on success, <0 on error
+
+Release Host Key ID (HKID) to allow more efficient reclaim of private memory.
+After this, the TD is no longer in a runnable state.
+
+Using KVM_TDX_TERMINATE_VM is optional.
+
+- id: KVM_TDX_TERMINATE_VM
+- flags: must be 0
+- data: must be 0
+- hw_error: must be 0
+
 KVM TDX creation flow
 =====================
 In addition to the standard KVM flow, new TDX ioctls need to be called.  The
arch/x86/include/uapi/asm/kvm.h +1 -0
index 225a12e0d5d6..a2f973e1d75d 100644
@@ -939,6 +939,7 @@ enum kvm_tdx_cmd_id {
 	KVM_TDX_INIT_MEM_REGION,
 	KVM_TDX_FINALIZE_VM,
 	KVM_TDX_GET_CPUID,
+	KVM_TDX_TERMINATE_VM,
 
 	KVM_TDX_CMD_NR_MAX,
 };
arch/x86/kvm/vmx/tdx.c +26 -15

78 lines not on this page · raw message

Signature · 1 line
2.43.0
#2 lore raw

Re: [PATCH V3 1/1] KVM: TDX: Add sub-ioctl KVM_TDX_TERMINATE_VM

arch/x86/kvm/vmx/tdx.c static int tdx_td_finalize(struct kvm *kvm, struct kvm_tdx_cmd *cmd) · line 2789

Quoted 3 lines · Adrian Hunter
arch/x86/kvm/vmx/tdx.c +3 -0
+static int tdx_terminate_vm(struct kvm *kvm)
+{
+	if (!kvm_trylock_all_vcpus(kvm))

Introduction of kvm_trylock_all_vcpus() is still in progress:

	https://lore.kernel.org/r/[email protected]/

but it has kvm_trylock_all_vcpus(kvm) return value the other way around, so this will instead need to be:

if (kvm_trylock_all_vcpus(kvm))

Quoted 24 lines
arch/x86/kvm/vmx/tdx.c +14 -0
+		return -EBUSY;
+
+	kvm_vm_dead(kvm);
+
+	kvm_unlock_all_vcpus(kvm);
+
+	tdx_mmu_release_hkid(kvm);
+
+	return 0;
+}
+
 int tdx_vm_ioctl(struct kvm *kvm, void __user *argp)
 {
 	struct kvm_tdx_cmd tdx_cmd;
@@ -2817,6 +2825,9 @@ int tdx_vm_ioctl(struct kvm *kvm, void __user *argp)
 	case KVM_TDX_FINALIZE_VM:
 		r = tdx_td_finalize(kvm, &tdx_cmd);
 		break;
+	case KVM_TDX_TERMINATE_VM:
+		r = tdx_terminate_vm(kvm);
+		break;
 	default:
 		r = -EINVAL;
 		goto out;
#3 lore raw

Re: [PATCH V3 1/1] KVM: TDX: Add sub-ioctl KVM_TDX_TERMINATE_VM

Quoted 7 lines · Adrian Hunter

arch/x86/kvm/vmx/tdx.c static int tdx_td_finalize(struct kvm *kvm, struct kvm_tdx_cmd *cmd) · line 2789

Quoted 3 lines · Adrian Hunter
arch/x86/kvm/vmx/tdx.c +3 -0
+static int tdx_terminate_vm(struct kvm *kvm)
+{
+	if (!kvm_trylock_all_vcpus(kvm))

Introduction of kvm_trylock_all_vcpus() is still in progress:

Quoted 7 lines
	https://lore.kernel.org/r/[email protected]/

but it has kvm_trylock_all_vcpus(kvm) return value the other way around, so this will instead need to be:

if (kvm_trylock_all_vcpus(kvm))

Sean, do you have any comments on this patch? Should I send out a new version with the change above?

Note kvm_trylock_all_vcpus() now in Linus' tree:

	https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e4a454ced74c0ac97c8bd32f086ee3ad74528780
#4 lore raw

Re: [PATCH V3 1/1] KVM: TDX: Add sub-ioctl KVM_TDX_TERMINATE_VM

In reply to Adrian Hunter
Quoted 6 lines · Adrian Hunter
arch/x86/kvm/vmx/tdx.c +0 -0
index b952bc673271..5161f6f891d7 100644
@@ -500,14 +500,7 @@ void tdx_mmu_release_hkid(struct kvm *kvm)
 	 */

arch/x86/kvm/vmx/tdx.c void tdx_mmu_release_hkid(struct kvm *kvm) · line 510

Quoted 10 lines
arch/x86/kvm/vmx/tdx.c +0 -7
 	mutex_lock(&tdx_lock);
 
-	/*
-	 * Releasing HKID is in vm_destroy().
-	 * After the above flushing vps, there should be no more vCPU
-	 * associations, as all vCPU fds have been released at this stage.
-	 */
 	err = tdh_mng_vpflushdone(&kvm_tdx->td);
-	if (err == TDX_FLUSHVP_NOT_DONE)
-		goto out;

This belongs in a separate patch, with a changelog explaining what's up. Because my original "suggestion"[1] was simply a question :-)

+ /* Uh, what's going on here? */
if (err == TDX_FLUSHVP_NOT_DONE)

You did all the hard work of tracking down the history, and as above, this definitely warrants its own changelog.

[1] https://lkml.kernel.org/r/Z-V0qyTn2bXdrPF7%40google.com
[2] https://lore.kernel.org/all/[email protected]

Quoted 23 lines
arch/x86/kvm/vmx/tdx.c +2 -1
 	if (KVM_BUG_ON(err, kvm)) {
 		pr_tdx_error(TDH_MNG_VPFLUSHDONE, err);
 		pr_err("tdh_mng_vpflushdone() failed. HKID %d is leaked.\n",
@@ -515,6 +508,7 @@ void tdx_mmu_release_hkid(struct kvm *kvm)
 		goto out;
 	}
 
+	write_lock(&kvm->mmu_lock);
 	for_each_online_cpu(i) {
 		if (packages_allocated &&
 		    cpumask_test_and_set_cpu(topology_physical_package_id(i),
@@ -539,7 +533,7 @@ void tdx_mmu_release_hkid(struct kvm *kvm)
 	} else {
 		tdx_hkid_free(kvm_tdx);
 	}
-
+	write_unlock(&kvm->mmu_lock);
 out:
 	mutex_unlock(&tdx_lock);
 	cpus_read_unlock();
@@ -1789,13 +1783,13 @@ int tdx_sept_remove_private_spte(struct kvm *kvm, gfn_t gfn,
 	struct page *page = pfn_to_page(pfn);
 	int ret;

arch/x86/kvm/vmx/tdx.c int tdx_sept_remove_private_spte(struct kvm *kvm, gfn_t gfn, · line 1787

Quoted 10 lines
arch/x86/kvm/vmx/tdx.c +2 -7
 
-	/*
-	 * HKID is released after all private pages have been removed, and set
-	 * before any might be populated. Warn if zapping is attempted when
-	 * there can't be anything populated in the private EPT.
-	 */
-	if (KVM_BUG_ON(!is_hkid_assigned(to_kvm_tdx(kvm)), kvm))
-		return -EINVAL;
+	if (!is_hkid_assigned(to_kvm_tdx(kvm))) {
+		WARN_ON_ONCE(!kvm->vm_dead);

Should this be a KVM_BUG_ON? I.e. to kill the VM? That'd set vm_dead, which is kinda neat, i.e. that it'd achieve what the warning is warning about :-)

Quoted 8 lines
arch/x86/kvm/vmx/tdx.c +5 -0
+		ret = tdx_reclaim_page(page);
+		if (!ret)
+			tdx_unpin(kvm, page);
+		return ret;
+	}
 
 	ret = tdx_sept_zap_private_spte(kvm, gfn, level, page);
 	if (ret <= 0)