From: Nikita Kalyazin <kalyazin@amazon.com>
To: Peter Xu <peterx@redhat.com>
Cc: <akpm@linux-foundation.org>, <pbonzini@redhat.com>,
<shuah@kernel.org>, <viro@zeniv.linux.org.uk>,
<brauner@kernel.org>, <muchun.song@linux.dev>, <hughd@google.com>,
<kvm@vger.kernel.org>, <linux-kselftest@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<linux-fsdevel@vger.kernel.org>, <jack@suse.cz>,
<lorenzo.stoakes@oracle.com>, <Liam.Howlett@oracle.com>,
<jannh@google.com>, <ryan.roberts@arm.com>, <david@redhat.com>,
<jthoughton@google.com>, <graf@amazon.de>, <jgowans@amazon.com>,
<roypat@amazon.co.uk>, <derekmn@amazon.com>, <nsaenz@amazon.es>,
<xmarcalx@amazon.com>
Subject: Re: [PATCH v3 4/6] KVM: guest_memfd: add support for userfaultfd minor
Date: Wed, 11 Jun 2025 13:09:36 +0100 [thread overview]
Message-ID: <dd851cab-eb22-40ae-b926-6f0eb1567299@amazon.com> (raw)
In-Reply-To: <aEiwvi-oqfTiyP3s@x1.local>
On 10/06/2025 23:25, Peter Xu wrote:
> On Fri, Apr 04, 2025 at 03:43:50PM +0000, Nikita Kalyazin wrote:
>> Add support for sending a pagefault event if userfaultfd is registered.
>> Only page minor event is currently supported.
>>
>> Signed-off-by: Nikita Kalyazin <kalyazin@amazon.com>
>> ---
>> virt/kvm/guest_memfd.c | 10 ++++++++++
>> 1 file changed, 10 insertions(+)
>>
>> diff --git a/virt/kvm/guest_memfd.c b/virt/kvm/guest_memfd.c
>> index fbf89e643add..096d89e7282d 100644
>> --- a/virt/kvm/guest_memfd.c
>> +++ b/virt/kvm/guest_memfd.c
>> @@ -4,6 +4,9 @@
>> #include <linux/kvm_host.h>
>> #include <linux/pagemap.h>
>> #include <linux/anon_inodes.h>
>> +#ifdef CONFIG_KVM_PRIVATE_MEM
>> +#include <linux/userfaultfd_k.h>
>> +#endif /* CONFIG_KVM_PRIVATE_MEM */
>>
>> #include "kvm_mm.h"
>>
>> @@ -380,6 +383,13 @@ static vm_fault_t kvm_gmem_fault(struct vm_fault *vmf)
>> kvm_gmem_mark_prepared(folio);
>> }
>>
>> + if (userfaultfd_minor(vmf->vma) &&
>> + !(vmf->flags & FAULT_FLAG_USERFAULT_CONTINUE)) {
>> + folio_unlock(folio);
>> + filemap_invalidate_unlock_shared(inode->i_mapping);
>> + return handle_userfault(vmf, VM_UFFD_MINOR);
>> + }
>> +
>
> Hmm, does guest-memfd (when with your current approach) at least needs to
> define the new can_userfault() hook?
>
> Meanwhile, we have some hard-coded lines so far, like:
>
> mfill_atomic():
> if (!vma_is_shmem(dst_vma) &&
> uffd_flags_mode_is(flags, MFILL_ATOMIC_CONTINUE))
> goto out_unlock;
>
> I thought it would fail guest-memfd already on a CONTINUE request, and it
> doesn't seem to be touched yet in this series.
>
> I'm not yet sure how the test worked out without hitting things like it.
> Highly likely I missed something. Some explanations would be welcomed..
Yes, I realised that I'd failed to post this part soon after I sent the
series, but I refrained from sending a new version because the upstream
consensus was to review/merge the mmap support in guest_memfd [1] before
continuing to build on top of it. This is the missed part I planned to
include in the next version. Sorry for the confusion.
diff --git a/include/linux/userfaultfd_k.h b/include/linux/userfaultfd_k.h
index 64551e8a55fb..080437fa7eab 100644
--- a/include/linux/userfaultfd_k.h
+++ b/include/linux/userfaultfd_k.h
@@ -221,8 +221,10 @@ static inline bool vma_can_userfault(struct
vm_area_struct *vma,
if (vm_flags & VM_DROPPABLE)
return false;
- if (!vma->vm_ops->can_userfault ||
- !vma->vm_ops->can_userfault(vma, VM_UFFD_MINOR))
+ if ((vm_flags & VM_UFFD_MINOR) &&
+ (!vma->vm_ops ||
+ !vma->vm_ops->can_userfault ||
+ !vma->vm_ops->can_userfault(vma, VM_UFFD_MINOR)))
return false;
/*
diff --git a/mm/userfaultfd.c b/mm/userfaultfd.c
index 0aa82c968e16..638360a78561 100644
--- a/mm/userfaultfd.c
+++ b/mm/userfaultfd.c
@@ -788,7 +788,9 @@ static __always_inline ssize_t mfill_atomic(struct
userfaultfd_ctx *ctx,
return mfill_atomic_hugetlb(ctx, dst_vma, dst_start,
src_start, len, flags);
- can_userfault = dst_vma->vm_ops->can_userfault &&
+ can_userfault =
+ dst_vma->vm_ops &&
+ dst_vma->vm_ops->can_userfault &&
dst_vma->vm_ops->can_userfault(dst_vma, __VM_UFFD_FLAGS);
if (!vma_is_anonymous(dst_vma) && !can_userfault)
diff --git a/virt/kvm/guest_memfd.c b/virt/kvm/guest_memfd.c
index 91ee5dd91c31..202b12dc4b6f 100644
--- a/virt/kvm/guest_memfd.c
+++ b/virt/kvm/guest_memfd.c
@@ -420,8 +420,15 @@ static vm_fault_t kvm_gmem_fault(struct vm_fault *vmf)
return ret;
}
+static bool kvm_gmem_can_userfault(struct vm_area_struct *vma,
+ unsigned long vm_flags)
+{
+ return vm_flags & VM_UFFD_MINOR;
+}
+
static const struct vm_operations_struct kvm_gmem_vm_ops = {
- .fault = kvm_gmem_fault,
+ .fault = kvm_gmem_fault,
+ .can_userfault = kvm_gmem_can_userfault,
};
static int kvm_gmem_mmap(struct file *file, struct vm_area_struct *vma)
[1] https://lore.kernel.org/kvm/20250605153800.557144-1-tabba@google.com/
>
> Thanks,
>
>> vmf->page = folio_file_page(folio, vmf->pgoff);
>>
>> out_folio:
>> --
>> 2.47.1
>>
>
> --
> Peter Xu
>
next prev parent reply other threads:[~2025-06-11 12:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 15:43 [PATCH v3 0/6] KVM: guest_memfd: support for uffd minor Nikita Kalyazin
2025-04-04 15:43 ` [PATCH v3 1/6] mm: userfaultfd: generic continue for non hugetlbfs Nikita Kalyazin
2025-06-10 22:22 ` Peter Xu
2025-06-11 12:09 ` Nikita Kalyazin
2025-06-11 12:56 ` Peter Xu
2025-06-20 12:00 ` Nikita Kalyazin
2025-06-20 15:21 ` Peter Xu
2025-06-20 16:51 ` Nikita Kalyazin
2025-04-04 15:43 ` [PATCH v3 2/6] mm: provide can_userfault vma operation Nikita Kalyazin
2025-04-04 15:43 ` [PATCH v3 3/6] mm: userfaultfd: use " Nikita Kalyazin
2025-04-04 15:43 ` [PATCH v3 4/6] KVM: guest_memfd: add support for userfaultfd minor Nikita Kalyazin
2025-06-10 22:25 ` Peter Xu
2025-06-11 12:09 ` Nikita Kalyazin [this message]
2025-04-04 15:43 ` [PATCH v3 5/6] mm: userfaultfd: add UFFD_FEATURE_MINOR_GUEST_MEMFD Nikita Kalyazin
2025-04-04 15:43 ` [PATCH v3 6/6] KVM: selftests: test userfaultfd minor for guest_memfd Nikita Kalyazin
2025-04-04 16:33 ` [PATCH v3 0/6] KVM: guest_memfd: support for uffd minor Lorenzo Stoakes
2025-04-04 16:56 ` Nikita Kalyazin
2025-04-04 16:59 ` Lorenzo Stoakes
2025-04-04 17:12 ` Liam R. Howlett
2025-04-07 11:04 ` Nikita Kalyazin
2025-04-07 13:40 ` Liam R. Howlett
2025-04-07 14:04 ` Nikita Kalyazin
2025-04-07 14:24 ` Liam R. Howlett
2025-04-07 14:46 ` David Hildenbrand
2025-04-07 15:14 ` Lorenzo Stoakes
2025-04-07 15:26 ` David Hildenbrand
2025-04-08 8:20 ` Christian Brauner
2025-04-08 13:15 ` Ackerley Tng
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=dd851cab-eb22-40ae-b926-6f0eb1567299@amazon.com \
--to=kalyazin@amazon.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=david@redhat.com \
--cc=derekmn@amazon.com \
--cc=graf@amazon.de \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=jgowans@amazon.com \
--cc=jthoughton@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-fsdevel@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=muchun.song@linux.dev \
--cc=nsaenz@amazon.es \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=roypat@amazon.co.uk \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=xmarcalx@amazon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).