All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Michael Roth <michael.roth@amd.com>
Cc: <qemu-devel@nongnu.org>,  <pbonzini@redhat.com>,
	<pankaj.gupta@amd.com>,  <xiaoyao.li@intel.com>,
	<chao.p.peng@linux.intel.com>,  <david@kernel.org>,
	<berrange@redhat.com>,  Peter Xu <peterx@redhat.com>,
	 Fabiano Rosas <farosas@suse.de>
Subject: Re: [PATCH v7 10/12] hostmem: Support fully shared guest memfd to back a VM
Date: Wed, 30 Sep 2026 07:13:48 +0200	[thread overview]
Message-ID: <87qzibtj77.fsf@pond.sub.org> (raw)
In-Reply-To: <20260929235109.1398509-11-michael.roth@amd.com> (Michael Roth's message of "Tue, 29 Sep 2026 18:50:16 -0500")

Michael Roth <michael.roth@amd.com> writes:

> From: Peter Xu <peterx@redhat.com>
>
> Host backends supports guest-memfd now by detecting whether it's a
> confidential VM.  There's no way to choose it yet from the memory level to
> use it fully shared.  If we use guest-memfd, it so far always implies we
> need two layers of memory backends, while the guest-memfd only provides the
> private set of pages.
>
> This patch introduces a way so that QEMU can consume guest memfd as the
> only source of memory to back the object (aka, fully shared).
>
> To use the fully shared guest-memfd, one can add a memfd object with:
>
>   -object memory-backend-memfd,x-guest-memfd=on,share=on
>
> Note that share=on is required with fully shared guest_memfd.
>
> Since guest-memfd is not yet a drop-in replacement for memfd (e.g. lack
> of hugepage support), the option is tagged as experimental for now so
> that it can be made available for early enablement/testing without
> causing any surprises for other users.
>
> PS: there's a trivial touch-up on fd<0 check, because the stub to create
> guest-memfd may return negative but not -1.
>
> Reviewed-by: Xiaoyao Li <xiaoyao.li@intel.com>
> Reviewed-by: Fabiano Rosas <farosas@suse.de>
> Reviewed-by: David Hildenbrand <david@kernel.org>
> Signed-off-by: Peter Xu <peterx@redhat.com>
> [mdr: add accompanying guest-memfd doc, mark as experimental]
> Co-developed-by: Michael Roth <michael.roth@amd.com>
> Signed-off-by: Michael Roth <michael.roth@amd.com>

QAPI schema
Acked-by: Markus Armbruster <armbru@redhat.com>



  reply	other threads:[~2026-09-30  5:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 23:50 [PATCH v7 00/12] KVM/hostmem: Support init-shared guest-memfd as VM backends Michael Roth
2026-09-29 23:50 ` [PATCH v7 01/12] kvm: Decouple memory attribute check from kvm_guest_memfd_supported Michael Roth
2026-09-29 23:50 ` [PATCH v7 02/12] kvm: Detect guest-memfd flags supported Michael Roth
2026-09-29 23:50 ` [PATCH v7 03/12] kvm: Provide explicit error for kvm_create_guest_memfd() Michael Roth
2026-09-29 23:50 ` [PATCH v7 04/12] ramblock: Rename guest_memfd to guest_memfd_private Michael Roth
2026-09-29 23:50 ` [PATCH v7 05/12] memory: Rename RAM_GUEST_MEMFD to RAM_GUEST_MEMFD_PRIVATE Michael Roth
2026-09-29 23:50 ` [PATCH v7 06/12] memory: Rename memory_region_has_guest_memfd() to *_private() Michael Roth
2026-09-29 23:50 ` [PATCH v7 07/12] hostmem: Rename guest_memfd to guest_memfd_private Michael Roth
2026-09-29 23:50 ` [PATCH v7 08/12] machine: Rename machine_require_guest_memfd() to *_private() Michael Roth
2026-09-29 23:50 ` [PATCH v7 09/12] memory: Rename memory_region_init_ram_guest_memfd() " Michael Roth
2026-09-29 23:50 ` [PATCH v7 10/12] hostmem: Support fully shared guest memfd to back a VM Michael Roth
2026-09-30  5:13   ` Markus Armbruster [this message]
2026-09-30 15:10     ` Peter Xu
2026-09-29 23:50 ` [PATCH v7 11/12] tests/migration-test: Support guest-memfd init shared mem type Michael Roth
2026-09-29 23:50 ` [PATCH v7 12/12] tests/migration-test: Add a precopy test for guest-memfd Michael Roth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87qzibtj77.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=chao.p.peng@linux.intel.com \
    --cc=david@kernel.org \
    --cc=farosas@suse.de \
    --cc=michael.roth@amd.com \
    --cc=pankaj.gupta@amd.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=xiaoyao.li@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.