On Fri, May 22, 2026, Ackerley Tng wrote: > Update the guest_memfd populate() flow to pull memory attributes from the > gmem instance instead of the VM when KVM is not configured to track > shared/private status in the VM. > > Rename the per-VM API to make it clear that it retrieves per-VM > attributes, i.e. is not suitable for use outside of flows that are > specific to generic per-VM attributes. > > Co-developed-by: Sean Christopherson <[email protected]> > Signed-off-by: Sean Christopherson <[email protected]> > Reviewed-by: Fuad Tabba <[email protected]> > Signed-off-by: Ackerley Tng <[email protected]>
We should squash this in with the previous patch, i.e. wire up PRIVATE to gmem in a single patch (sans the ioctl support). I had a hell of time figure out how the range-based lookup was supposed to work when revisiting the "wire up" patch, until I realized populate() was handled in the next patch.
