On Tue, 2025-07-08 at 11:03 -0700, Sean Christopherson wrote: > > I think there is interest in de-coupling it? > > No? I'm talking about the intra-host migration/reboot optimization stuff. And not doing a good job, sorry. > Even if we get to a point where multiple distinct VMs can bind to a single > guest_memfd, e.g. for inter-VM shared memory, there will still need to be a > sole > owner of the memory. AFAICT, fully decoupling guest_memfd from a VM would add > non-trivial complexity for zero practical benefit. I'm talking about moving a gmem fd between different VMs or something using KVM_LINK_GUEST_MEMFD [0]. Not advocating to try to support it. But trying to feel out where the concepts are headed. It kind of allows gmem fds (or just their source memory?) to live beyond a VM lifecycle. [0] https://lore.kernel.org/all/cover.1747368092.git.afranji@xxxxxxxxxx/ https://lore.kernel.org/kvm/cover.1749672978.git.afranji@xxxxxxxxxx/
