From: Nikita Kalyazin <kalyazin@amazon.com>
To: Peter Xu <peterx@redhat.com>
Cc: Mike Rapoport <rppt@kernel.org>, <linux-mm@kvack.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
David Hildenbrand <david@redhat.com>,
"Hugh Dickins" <hughd@google.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Michal Hocko <mhocko@suse.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Shuah Khan <shuah@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@suse.cz>, <linux-kernel@vger.kernel.org>,
<kvm@vger.kernel.org>, <linux-kselftest@vger.kernel.org>
Subject: Re: [RFC PATCH 0/4] mm, kvm: add guest_memfd support for uffd minor faults
Date: Wed, 19 Nov 2025 17:35:32 +0000 [thread overview]
Message-ID: <b51a9cad-7942-473d-971a-d6fa3b26f63e@amazon.com> (raw)
In-Reply-To: <aRt52tDCh72ytIp1@x1.local>
On 17/11/2025 19:39, Peter Xu wrote:
> On Mon, Nov 17, 2025 at 05:55:46PM +0000, Nikita Kalyazin wrote:
>> In our use case, Firecracker snapshot-restore using UFFD [1], we will use
>> UFFD minor/continue to respond to guest_memfd faults in user mappings
>> primarily due to VMM accesses that are required for PV (virtio) device
>> emulation and also KVM accesses when decoding MMIO operations on x86.
>
> I'm curious if firecracker plans to support live snapshot save. When with
> something like ioctls_supported flags, guest-memfd can declare support for
> wr-protect support easily too, and synchronous userfaultfd wr-protect traps
> will be an efficient way to do live save.
>
> I'm guessing it's not an immediate demand now or it would have been asked
> already supporting both MINOR and WP, but I just want to raise this
> question. Qemu already supports live snapshot save, so it'll always be
> good gmem can also support wp at some point, but it can be done later too.
No, live snapshots haven't been on our plan so far.
>
> Thanks,
>
> --
> Peter Xu
>
prev parent reply other threads:[~2025-11-19 17:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 11:46 Mike Rapoport
2025-11-17 11:46 ` [RFC PATCH 1/4] userfaultfd: move vma_can_userfault out of line Mike Rapoport
2025-11-17 17:00 ` David Hildenbrand (Red Hat)
2025-11-17 11:46 ` [RFC PATCH 2/4] userfaultfd, shmem: use a VMA callback to handle UFFDIO_CONTINUE Mike Rapoport
2025-11-17 17:08 ` David Hildenbrand (Red Hat)
2025-11-21 11:52 ` Mike Rapoport
2025-11-17 11:46 ` [RFC PATCH 3/4] userfaultfd, guest_memfd: support userfault minor mode in guest_memfd Mike Rapoport
2025-11-18 16:41 ` David Hildenbrand (Red Hat)
2025-11-21 11:59 ` Mike Rapoport
2025-11-17 11:46 ` [RFC PATCH 4/4] KVM: selftests: test userfaultfd minor for guest_memfd Mike Rapoport
2025-11-17 17:55 ` [RFC PATCH 0/4] mm, kvm: add guest_memfd support for uffd minor faults Nikita Kalyazin
2025-11-17 19:39 ` Peter Xu
2025-11-19 17:35 ` Nikita Kalyazin [this message]
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=b51a9cad-7942-473d-971a-d6fa3b26f63e@amazon.com \
--to=kalyazin@amazon.com \
--cc=Liam.Howlett@oracle.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=rppt@kernel.org \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox