[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6136a419b8de3b7b3205dfb0cd85327c58c8ce54.camel@intel.com>
Date: Wed, 18 Jun 2025 22:07:07 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "Annapurve, Vishal" <vannapurve@...gle.com>, "Hunter, Adrian"
<adrian.hunter@...el.com>
CC: "Gao, Chao" <chao.gao@...el.com>, "seanjc@...gle.com" <seanjc@...gle.com>,
"Huang, Kai" <kai.huang@...el.com>, "binbin.wu@...ux.intel.com"
<binbin.wu@...ux.intel.com>, "Chatre, Reinette" <reinette.chatre@...el.com>,
"Li, Xiaoyao" <xiaoyao.li@...el.com>, "kirill.shutemov@...ux.intel.com"
<kirill.shutemov@...ux.intel.com>, "tony.lindgren@...ux.intel.com"
<tony.lindgren@...ux.intel.com>, "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"pbonzini@...hat.com" <pbonzini@...hat.com>, "Yamahata, Isaku"
<isaku.yamahata@...el.com>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "Zhao, Yan Y" <yan.y.zhao@...el.com>
Subject: Re: [PATCH V4 1/1] KVM: TDX: Add sub-ioctl KVM_TDX_TERMINATE_VM
On Tue, 2025-06-17 at 23:00 -0700, Vishal Annapurve wrote:
> gmem link support[1] allows associating existing guest_memfds with new
> VM instances.
>
> Breakdown of the userspace VMM flow:
> 1) Create a new VM instance before closing guest_memfd files.
> 2) Link existing guest_memfd files with the new VM instance. -> This
> creates new set of files backed by the same inode but associated with
> the new VM instance.
> 3) Close the older guest memfd handles -> results in older VM instance cleanup.
>
> [1] https://lore.kernel.org/lkml/cover.1747368092.git.afranji@google.com/#t
Is it intended to even work for TDX private memory? It seems to be SEV focused.
I think we really need to come to an agreement on how much to design code around
future ideas vs a more iterative approach. I had thought we had...
Powered by blists - more mailing lists