On 12/16/2025 4:51 AM, Peter Xu wrote:
This name is too generic, and can conflict with in-place guest-memfd
support.  Add a _PRIVATE suffix to show what it really means: it is always
silently using an internal guest-memfd to back a shared host backend,
rather than used in-place.

This paves way for in-place guest-memfd, which means we can have a ramblock
that allocates pages completely from guest-memfd (private or shared).

Well, the term of "in-place" needs to be changed to "init-shared".

Reply via email to