Re: [PATCH v4 00/12] KVM/hostmem: Support init-shared guest-memfd as VM backends

Michael Roth <[email protected]>
Newsgroups org.nongnu.qemu-devel
Message-ID <3fwr25hmoz7yicoh3o3x3ldeweapn2tbn4dnji67hgrnz7l5bh@rs7gqotxraef>
On Fri, Aug 21, 2026 at 10:18:26AM -0400, Peter Xu wrote:
> On Wed, Aug 12, 2026 at 03:16:38PM -0500, Michael Roth wrote:
> > v1: https://lore.kernel.org/r/[email protected]
> > v2: https://lore.kernel.org/r/[email protected]
> > v3: https://lore.kernel.org/r/[email protected]/
> > v4:
> > - Picked up v3 series from Peter Xu and rebased on 11.1.0
> > - Collected pending Reviewed-by's
> > - Per-patch changes:
> >   [01/12] Fix blank space (Xiaoyao)
> >           Fix commit message typos
> >   [02/12] Drop duplicated error-handling for capability checks
> >   [05/12] Fix up commit message, disambigurate "in-place" terminology (Xiaoyao)
> >   [07/12] Fix up commit message, disambigurate "in-place" terminology (Xiaoyao)
> >   [08/12] Disallow 'seal' and 'hugetlb' options based on guest-memfd=on
> >           Fix minor typo in comment
> >   [11/12] Fix up typo in g_test_skip() reason
> >           Pending: Move kvm_guest_memfd_init_shared_supported() to
> >             migration-util.c (Fabiano)
> > 
> > This patchset is also available at:
> > 
> >   https://github.com/amdese/qemu/commits/gmem-shared-mem-v4
> > 
> > and is based on top of v11.1.0
> 
> Should I just pick this up?  I'll touch up the commit log that Phil
> requested.  Objections welcomed before next week.

Hi Peter,

No objection here, although I'll be posting new version of the in-place
conversion support later this week (~Wed-ish) and was planning to an
updated version of this series roughly the same time so which ever way
is best for you.

If you do post one though there's also the missing 'return false' and
dropping the seal=off enforcement that Daniel noticed before we started
talking about introspection fun.

Thanks!

-Mike

> 
> -- 
> Peter Xu
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.