Re: [RFC PATCH 0/9] mm: Memory providers for guest_memfd and iommufd

[David Woodhouse]

On Mon, 2026-10-12 at 15:07 +0000, Fred Griffoul wrote:
>  Devices are different, because a device may not support
> faults. So the provider also revokes the range on the target once it
> owns the frames, and iommufd maps them right away. In other words, a
> revoke means that the frames behind a range changed, whether they went
> away or arrived.

That would map to the IOMMUFD 'REPLACE' operation that hitlessly
replaces a PTE, but does anyone actually need that?

As I said, assume that the "crappy devices can't take faults and need a
scratch patch" issue is dealt with *elsewhere* and not relevant to the
guest_memfd/memprovider work. That's purely a quirk on a given IOAS
within iommufd.

Attachment: smime.p7s
Description: S/MIME cryptographic signature