From: Nikita Kalyazin <kalyazin@amazon.com>
To: Mike Rapoport <rppt@kernel.org>, <linux-mm@kvack.org>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Axel Rasmussen <axelrasmussen@google.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
David Hildenbrand <david@redhat.com>,
Hugh Dickins <hughd@google.com>,
James Houghton <jthoughton@google.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
"Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>,
Michal Hocko <mhocko@suse.com>,
"Muchun Song" <muchun.song@linux.dev>,
Oscar Salvador <osalvador@suse.de>,
"Paolo Bonzini" <pbonzini@redhat.com>,
Peter Xu <peterx@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: [PATCH RFC 15/17] KVM: guest_memfd: implement userfaultfd missing mode
Date: Wed, 4 Mar 2026 17:12:59 +0000 [thread overview]
Message-ID: <90cf68db-2e21-4153-8eb6-2c8ffb398d0d@amazon.com> (raw)
In-Reply-To: <20260127192936.1250096-16-rppt@kernel.org>
On 27/01/2026 19:29, Mike Rapoport wrote:
> From: Nikita Kalyazin <kalyazin@amazon.com>
>
> userfaultfd missing mode allows populating guest memory with the content
> supplied by userspace on demand.
>
> Extend guest_memfd implementation of vm_uffd_ops to support MISSING
> mode.
>
> Signed-off-by: Nikita Kalyazin <kalyazin@amazon.com>
> Co-developed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> ---
> virt/kvm/guest_memfd.c | 60 +++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 59 insertions(+), 1 deletion(-)
>
> diff --git a/virt/kvm/guest_memfd.c b/virt/kvm/guest_memfd.c
> index 087e7632bf70..14cca057fc0e 100644
> --- a/virt/kvm/guest_memfd.c
> +++ b/virt/kvm/guest_memfd.c
> @@ -431,6 +431,14 @@ static vm_fault_t kvm_gmem_fault_user_mapping(struct vm_fault *vmf)
> ret = VM_FAULT_UFFD_MINOR;
> goto out_folio;
> }
> +
> + /*
> + * Check if userfaultfd is registered in missing mode. If so,
> + * check if a folio exists in the page cache. If not, return
> + * VM_FAULT_UFFD_MISSING to trigger the userfaultfd handler.
> + */
> + if (userfaultfd_missing(vmf->vma) && IS_ERR_OR_NULL(folio))
> + return VM_FAULT_UFFD_MISSING;
> }
>
> /* folio not in the pagecache, try to allocate */
> @@ -507,9 +515,59 @@ static bool kvm_gmem_can_userfault(struct vm_area_struct *vma, vm_flags_t vm_fla
> return true;
> }
>
> +static struct folio *kvm_gmem_folio_alloc(struct vm_area_struct *vma,
> + unsigned long addr)
> +{
> + struct inode *inode = file_inode(vma->vm_file);
> + pgoff_t pgoff = linear_page_index(vma, addr);
> + struct mempolicy *mpol;
> + struct folio *folio;
> + gfp_t gfp;
> +
> + if (unlikely(pgoff >= (i_size_read(inode) >> PAGE_SHIFT)))
> + return NULL;
> +
> + gfp = mapping_gfp_mask(inode->i_mapping);
> + mpol = mpol_shared_policy_lookup(&GMEM_I(inode)->policy, pgoff);
> + mpol = mpol ?: get_task_policy(current);
> + folio = folio_alloc_mpol(gfp, 0, mpol, pgoff, numa_node_id());
It looks like folio_alloc_mpol_noprof() and filemap_remove_folio() are
not actually exported to modules. Would it be ok to export them similar
to how it was done in f634f10809ec ("mm/mempolicy: Export memory policy
symbols")?
diff --git a/mm/filemap.c b/mm/filemap.c
index 3e4579e4b8bb..041c7719e524 100644
--- a/mm/filemap.c
+++ b/mm/filemap.c
@@ -261,6 +261,7 @@ void filemap_remove_folio(struct folio *folio)
filemap_free_folio(mapping, folio);
}
+EXPORT_SYMBOL_FOR_MODULES(filemap_remove_folio, "kvm");
/*
* page_cache_delete_batch - delete several folios from page cache
diff --git a/mm/mempolicy.c b/mm/mempolicy.c
index 3d797d47a040..1dbbbb28a36e 100644
--- a/mm/mempolicy.c
+++ b/mm/mempolicy.c
@@ -2442,6 +2442,7 @@ struct folio *folio_alloc_mpol_noprof(gfp_t gfp,
unsigned int order,
set_page_refcounted(page);
return page_rmappable_folio(page);
}
+EXPORT_SYMBOL_FOR_MODULES(folio_alloc_mpol_noprof, "kvm");
/**
* vma_alloc_folio - Allocate a folio for a VMA.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f634f10809ec3d51d9529dfb0f99bc7cec1b5eff
> + mpol_cond_put(mpol);
> +
> + return folio;
> +}
> +
> +static int kvm_gmem_filemap_add(struct folio *folio,
> + struct vm_area_struct *vma,
> + unsigned long addr)
> +{
> + struct inode *inode = file_inode(vma->vm_file);
> + struct address_space *mapping = inode->i_mapping;
> + pgoff_t pgoff = linear_page_index(vma, addr);
> + int err;
> +
> + __folio_set_locked(folio);
> + err = filemap_add_folio(mapping, folio, pgoff, GFP_KERNEL);
> + if (err) {
> + folio_unlock(folio);
> + return err;
> + }
> +
> + return 0;
> +}
> +
> +static void kvm_gmem_filemap_remove(struct folio *folio,
> + struct vm_area_struct *vma)
> +{
> + filemap_remove_folio(folio);
> + folio_unlock(folio);
> +}
> +
> static const struct vm_uffd_ops kvm_gmem_uffd_ops = {
> - .can_userfault = kvm_gmem_can_userfault,
> + .can_userfault = kvm_gmem_can_userfault,
> .get_folio_noalloc = kvm_gmem_get_folio_noalloc,
> + .alloc_folio = kvm_gmem_folio_alloc,
> + .filemap_add = kvm_gmem_filemap_add,
> + .filemap_remove = kvm_gmem_filemap_remove,
> };
> #endif /* CONFIG_USERFAULTFD */
>
> --
> 2.51.0
>
next prev parent reply other threads:[~2026-03-04 17:13 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 19:29 [PATCH RFC 00/17] mm, kvm: allow uffd suppot in guest_memfd Mike Rapoport
2026-01-27 19:29 ` [PATCH RFC 01/17] userfaultfd: introduce mfill_copy_folio_locked() helper Mike Rapoport
2026-02-03 17:45 ` Peter Xu
2026-02-08 9:49 ` Mike Rapoport
2026-01-27 19:29 ` [PATCH RFC 02/17] userfaultfd: introduce struct mfill_state Mike Rapoport
2026-01-27 19:29 ` [PATCH RFC 03/17] userfaultfd: introduce mfill_get_pmd() helper Mike Rapoport
2026-01-27 19:29 ` [PATCH RFC 04/17] userfaultfd: introduce mfill_get_vma() and mfill_put_vma() Mike Rapoport
2026-02-02 21:49 ` Peter Xu
2026-02-08 9:54 ` Mike Rapoport
2026-01-27 19:29 ` [PATCH RFC 05/17] userfaultfd: retry copying with locks dropped in mfill_atomic_pte_copy() Mike Rapoport
2026-02-02 21:23 ` Peter Xu
2026-02-08 10:01 ` Mike Rapoport
2026-01-27 19:29 ` [PATCH RFC 06/17] userfaultfd: move vma_can_userfault out of line Mike Rapoport
2026-01-27 19:29 ` [PATCH RFC 07/17] userfaultfd: introduce vm_uffd_ops Mike Rapoport
2026-02-02 21:36 ` Peter Xu
2026-02-08 10:13 ` Mike Rapoport
2026-02-11 19:35 ` Peter Xu
2026-02-15 17:47 ` Mike Rapoport
2026-02-18 21:34 ` Peter Xu
2026-01-27 19:29 ` [PATCH RFC 08/17] userfaultfd, shmem: use a VMA callback to handle UFFDIO_CONTINUE Mike Rapoport
2026-01-27 19:29 ` [PATCH RFC 09/17] userfaultfd: introduce vm_uffd_ops->alloc_folio() Mike Rapoport
2026-02-02 22:13 ` Peter Xu
2026-02-08 10:22 ` Mike Rapoport
2026-02-11 19:37 ` Peter Xu
2026-01-27 19:29 ` [PATCH RFC 10/17] shmem, userfaultfd: implement shmem uffd operations using vm_uffd_ops Mike Rapoport
2026-02-03 17:40 ` Peter Xu
2026-02-08 10:35 ` Mike Rapoport
2026-02-11 20:00 ` Peter Xu
2026-02-15 17:45 ` Mike Rapoport
2026-02-18 21:45 ` Peter Xu
2026-01-27 19:29 ` [PATCH RFC 11/17] userfaultfd: mfill_atomic() remove retry logic Mike Rapoport
2026-01-27 19:29 ` [PATCH RFC 12/17] mm: introduce VM_FAULT_UFFD_MINOR fault reason Mike Rapoport
2026-01-27 19:29 ` [PATCH RFC 13/17] mm: introduce VM_FAULT_UFFD_MISSING " Mike Rapoport
2026-01-27 19:29 ` [PATCH RFC 14/17] KVM: guest_memfd: implement userfaultfd minor mode Mike Rapoport
2026-01-27 19:29 ` [PATCH RFC 15/17] KVM: guest_memfd: implement userfaultfd missing mode Mike Rapoport
2026-03-04 17:12 ` Nikita Kalyazin [this message]
2026-03-04 17:17 ` Nikita Kalyazin
2026-01-27 19:29 ` [PATCH RFC 16/17] KVM: selftests: test userfaultfd minor for guest_memfd Mike Rapoport
2026-01-27 19:29 ` [PATCH RFC 17/17] KVM: selftests: test userfaultfd missing " Mike Rapoport
2026-02-03 20:56 ` [PATCH RFC 00/17] mm, kvm: allow uffd suppot in guest_memfd Peter Xu
2026-02-09 15:35 ` David Hildenbrand (Arm)
2026-02-11 6:04 ` Mike Rapoport
2026-02-11 9:52 ` David Hildenbrand (Arm)
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=90cf68db-2e21-4153-8eb6-2c8ffb398d0d@amazon.com \
--to=kalyazin@amazon.com \
--cc=Liam.Howlett@oracle.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=jthoughton@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=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--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