Re: [PATCH v5 05/12] memory: Rename RAM_GUEST_MEMFD to RAM_GUEST_MEMFD_PRIVATE

[David Hildenbrand <david@kernel.org>]

On 9/8/26 15:30, Michael Roth wrote:
> From: Peter Xu <peterx@redhat.com>
> 
> This name is too generic, and can conflict with support for using
> guest-memfd for shared memory. Add a _PRIVATE suffix to show what it
> really means: it is using guest_memfd specifically for private memory;
> whether or not guest_memfd is being used for shared memory is something
> to be configured/determined separately.
> 
> This also paves way for in-place guest-memfd, which means we can have a
> ramblock that allocates pages completely from guest-memfd (private or
> shared).
> 
> Reviewed-by: Xiaoyao Li <xiaoyao.li@intel.com>
> Signed-off-by: Peter Xu <peterx@redhat.com>
> Reviewed-by: Michael Roth <michael.roth@amd.com>
> Signed-off-by: Michael Roth <michael.roth@amd.com>
> ---

Reviewed-by: David Hildenbrand <david@kernel.org>
-- 
Cheers,

David