On 9/2/26 21:46, Gregory Price wrote: > guest_memfd allocates its folios through a per-inode shared mempolicy. > > Today that policy can only be set after the fact, with mbind() on a host > mmap of the fd. That requires the fd to be mappable, and it cannot reach > folios that are only ever guest-faulted. Neither holds for a > non-mappable (confidential) guest_memfd.
That looks like an investment into a mechanism we will soon consider legacy, so I am not convinced this is the right approach? -- Cheers, David
