Re: [PATCH RFC v2 00/50] guest_memfd alternative providers

[Aneesh Kumar K . V]

Ackerley Tng via B4 Relay <devnull+ackerleytng.google.com@xxxxxxxxxx>
writes:

> Here's RFC v2 of guest_memfd alternative providers, continuing from "Allow
> guest_memfd to be created using a resource (pool) fd", which I'm considering
> RFC v1.
>

 [ ... 138 lines skipped ... ] 

>
> Aneesh, thanks for your series [4], I haven't got a chance to look at it yet. I
> will before I continue this prototype for IOMMU. I want to get feedback on this
> part first.
>

I am looking at rebasing my series on top of this one.

One detail we need to finalize is memory access through resource_fd. For
a VFIO fd, I believe we want to continue allowing access through that
fd. This means allowing read/write/mmap/ioctl, with the VFIO subsystem
accessors checking whether the memory is host-accessible before
accessing private PFNs [1]. My series denies mmap through the guest_memfd
fd.

https://lore.kernel.org/all/yq5a1p9qxmqg.fsf@xxxxxxxxxx


-aneesh