From: Peter Xu <peterx@redhat.com>
To: "Kiryl Shutsemau (Meta)" <kas@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>, Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@kernel.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Zi Yan <ziy@nvidia.com>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org,
kvm@vger.kernel.org, James Houghton <jthoughton@google.com>,
Andrea Arcangeli <aarcange@redhat.com>
Subject: Re: [RFC, PATCH 00/12] userfaultfd: working set tracking for VM guest memory
Date: Tue, 14 Apr 2026 11:28:33 -0400 [thread overview]
Message-ID: <ad5dIUpAMs4MuBvV@x1.local> (raw)
In-Reply-To: <20260414142354.1465950-1-kas@kernel.org>
Hi, Kiryl,
On Tue, Apr 14, 2026 at 03:23:34PM +0100, Kiryl Shutsemau (Meta) wrote:
> This series adds userfaultfd support for tracking the working set of
> VM guest memory, enabling VMMs to identify cold pages and evict them
> to tiered or remote storage.
Thanks for sharing this work, it looks very interesting to me.
Personally I am also looking at some kind of VMM memtiering issues. I'm
not sure if you saw my lsfmm proposal, it mentioned the challenge we're
facing, it's slightly different but still a bit relevant:
https://lore.kernel.org/all/aYuad2k75iD9bnBE@x1.local/
Unfortunately, that proposal was rejected upstream.
For us, it's so far more about migration and how migration process
introduce zero impact to guest workloads especially on hotness. I'm not
sure if we have any shared goals over that aspect.
>
> == Problem ==
>
> VMMs managing guest memory need to:
> 1. Track which pages are actively used (working set detection)
> 2. Safely evict cold pages to slower storage
> 3. Fetch pages back on demand when accessed again
>
> For shmem-backed guest memory, working set tracking partially works
> today: MADV_DONTNEED zaps PTEs while pages stay in page cache, and
> re-access auto-resolves from cache. But safe eviction still requires
> synchronous fault interception to prevent data loss races.
>
> For anonymous guest memory (needed for KSM cross-VM deduplication),
> there is no mechanism at all — clearing a PTE loses the page.
>
> == Solution ==
>
> The series introduces a unified userfaultfd interface that works
> across both anonymous and shmem-backed memory:
>
> UFFD_FEATURE_MINOR_ANON: extends MODE_MINOR registration to anonymous
> private memory. Uses the PROT_NONE hinting mechanism (same as NUMA
> balancing) to make pages inaccessible without freeing them.
>
> UFFD_FEATURE_MINOR_ASYNC: auto-resolves minor faults without handler
> involvement. The kernel restores PTE permissions immediately and the
> faulting thread continues. Works for anonymous, shmem, and hugetlbfs.
>
> UFFDIO_DEACTIVATE: marks pages as deactivated. For anonymous memory,
> sets PROT_NONE on PTEs (pages stay resident). For shmem/hugetlbfs,
> zaps PTEs (pages stay in page cache).
>
> UFFDIO_SET_MODE: toggles MINOR_ASYNC at runtime, synchronized via
> mmap_write_lock. Enables the VMM workflow: async mode for lightweight
> detection, sync mode for race-free eviction.
>
> PAGE_IS_UFFD_DEACTIVATED: PAGEMAP_SCAN category flag for efficient
> batch detection of cold (still-deactivated) anonymous pages.
>
> == VMM Workflow ==
AFAIU, this workflow provides two functionalities:
>
> UFFDIO_DEACTIVATE(all) -- async, no vCPU stalls
> sleep(interval)
> PAGEMAP_SCAN -- find cold pages
Until here it's only about page hotness tracking. I am curious whether you
evaluated idle page tracking. Is it because of perf overheads on rmap? To
me, your solution (until here.. on the hotness sampling) reads more like a
more efficient way to do idle page tracking but only per-mm, not per-folio.
That will also be something I would like to benefit if QEMU will decide to
do full userspace swap. I think that's our last resort, I'll likely start
with something that makes QEMU work together with Linux on swapping
(e.g. we're happy to make MGLRU or any reclaim logic that Linux mm
currently uses, as long as efficient) then QEMU only cares about the rest,
which is what the migration problem is about.
The other issue about idle page tracking to us is, I believe MGLRU
currently doesn't work well with it (due to ignoring IDLE bits) where the
old LRU algo works. I'm not sure how much you evaluated above, so it'll be
great to share from that perspective too. I also mentioned some of these
challenges in the lsfmm proposal link above.
> UFFDIO_SET_MODE(sync) -- block faults for eviction
> pwrite + MADV_DONTNEED cold pages -- safe, faults block
> UFFDIO_SET_MODE(async) -- resume tracking
These operations are the 2nd function. It's, IMHO, a full userspace swap
system based on userfaultfd.
Have you thought about directly relying on userfaultfd-wp to do this work?
The relevant question is, why do we need to block guest reads on pages
being evicted by the userapp? Can we still allow that to happen, which
seems to be more efficient? IIUC, only writes / updates matters in such
swap system.
Also, I'm not sure if you're aware of LLNL's umap library:
https://github.com/llnl/umap
That implemnted the swap system using userfaultfd wr-protect mode only, so
no new kernel API needed.
Thanks,
>
> The same workflow applies to shmem, with a different PAGEMAP_SCAN mask
> (!PAGE_IS_PRESENT instead of PAGE_IS_UFFD_DEACTIVATED).
>
> == NUMA Balancing ==
>
> NUMA balancing scanning is skipped on anonymous VM_UFFD_MINOR VMAs to
> avoid protnone conflicts. NUMA locality stats are fed from the uffd
> fault path via task_numa_fault() so the scheduler retains placement
> data. Shmem VMAs are unaffected (UFFDIO_DEACTIVATE zaps PTEs there,
> no protnone involved).
>
> == Testing ==
>
> The series includes 6 new selftests covering async/sync modes,
> PAGEMAP_SCAN cold detection, GUP through protnone, UFFDIO_SET_MODE
> toggling, and cleanup on close. All 73 uffd unit tests pass
> (including hugetlb) across defconfig, allnoconfig, allmodconfig,
> and randomized configs.
>
> Kiryl Shutsemau (Meta) (12):
> userfaultfd: define UAPI constants for anonymous minor faults
> userfaultfd: add UFFD_FEATURE_MINOR_ANON registration support
> userfaultfd: implement UFFDIO_DEACTIVATE ioctl
> userfaultfd: UFFDIO_CONTINUE for anonymous memory
> mm: intercept protnone faults on VM_UFFD_MINOR anonymous VMAs
> userfaultfd: auto-resolve shmem and hugetlbfs minor faults in async
> mode
> sched/numa: skip scanning anonymous VM_UFFD_MINOR VMAs
> userfaultfd: enable UFFD_FEATURE_MINOR_ANON
> mm/pagemap: add PAGE_IS_UFFD_DEACTIVATED to PAGEMAP_SCAN
> userfaultfd: add UFFDIO_SET_MODE for runtime sync/async toggle
> selftests/mm: add userfaultfd anonymous minor fault tests
> Documentation/userfaultfd: document working set tracking
>
> Documentation/admin-guide/mm/userfaultfd.rst | 141 ++++-
> fs/proc/task_mmu.c | 11 +-
> fs/userfaultfd.c | 184 +++++-
> include/linux/huge_mm.h | 6 +
> include/linux/mm.h | 2 +
> include/linux/sched/numa_balancing.h | 1 +
> include/linux/userfaultfd_k.h | 21 +-
> include/trace/events/sched.h | 3 +-
> include/uapi/linux/fs.h | 1 +
> include/uapi/linux/userfaultfd.h | 40 +-
> kernel/sched/fair.c | 13 +
> mm/huge_memory.c | 33 +-
> mm/hugetlb.c | 3 +-
> mm/memory.c | 51 +-
> mm/mprotect.c | 9 +-
> mm/shmem.c | 3 +-
> mm/userfaultfd.c | 164 +++++-
> tools/testing/selftests/mm/uffd-unit-tests.c | 458 +++++++++++++++
> 18 files changed, 1096 insertions(+), 48 deletions(-)
>
> Kiryl Shutsemau (Meta) (12):
> userfaultfd: define UAPI constants for anonymous minor faults
> userfaultfd: add UFFD_FEATURE_MINOR_ANON registration support
> userfaultfd: implement UFFDIO_DEACTIVATE ioctl
> userfaultfd: UFFDIO_CONTINUE for anonymous memory
> mm: intercept protnone faults on VM_UFFD_MINOR anonymous VMAs
> userfaultfd: auto-resolve shmem and hugetlbfs minor faults in async
> mode
> sched/numa: skip scanning anonymous VM_UFFD_MINOR VMAs
> userfaultfd: enable UFFD_FEATURE_MINOR_ANON
> mm/pagemap: add PAGE_IS_UFFD_DEACTIVATED to PAGEMAP_SCAN
> userfaultfd: add UFFDIO_SET_MODE for runtime sync/async toggle
> selftests/mm: add userfaultfd anonymous minor fault tests
> Documentation/userfaultfd: document working set tracking
>
> Documentation/admin-guide/mm/userfaultfd.rst | 141 +++++-
> fs/proc/task_mmu.c | 11 +-
> fs/userfaultfd.c | 184 +++++++-
> include/linux/huge_mm.h | 6 +
> include/linux/mm.h | 2 +
> include/linux/sched/numa_balancing.h | 1 +
> include/linux/userfaultfd_k.h | 21 +-
> include/trace/events/sched.h | 3 +-
> include/uapi/linux/fs.h | 1 +
> include/uapi/linux/userfaultfd.h | 40 +-
> kernel/sched/fair.c | 13 +
> mm/huge_memory.c | 33 +-
> mm/hugetlb.c | 3 +-
> mm/memory.c | 51 ++-
> mm/mprotect.c | 9 +-
> mm/shmem.c | 3 +-
> mm/userfaultfd.c | 164 ++++++-
> tools/testing/selftests/mm/uffd-unit-tests.c | 458 +++++++++++++++++++
> 18 files changed, 1096 insertions(+), 48 deletions(-)
>
> --
> 2.51.2
>
>
--
Peter Xu
next prev parent reply other threads:[~2026-04-14 15:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 14:23 Kiryl Shutsemau (Meta)
2026-04-14 14:23 ` [RFC, PATCH 01/12] userfaultfd: define UAPI constants for anonymous minor faults Kiryl Shutsemau (Meta)
2026-04-14 14:23 ` [RFC, PATCH 02/12] userfaultfd: add UFFD_FEATURE_MINOR_ANON registration support Kiryl Shutsemau (Meta)
2026-04-14 14:23 ` [RFC, PATCH 03/12] userfaultfd: implement UFFDIO_DEACTIVATE ioctl Kiryl Shutsemau (Meta)
2026-04-14 14:23 ` [RFC, PATCH 04/12] userfaultfd: UFFDIO_CONTINUE for anonymous memory Kiryl Shutsemau (Meta)
2026-04-14 14:23 ` [RFC, PATCH 05/12] mm: intercept protnone faults on VM_UFFD_MINOR anonymous VMAs Kiryl Shutsemau (Meta)
2026-04-14 14:23 ` [RFC, PATCH 06/12] userfaultfd: auto-resolve shmem and hugetlbfs minor faults in async mode Kiryl Shutsemau (Meta)
2026-04-14 14:23 ` [RFC, PATCH 07/12] sched/numa: skip scanning anonymous VM_UFFD_MINOR VMAs Kiryl Shutsemau (Meta)
2026-04-14 14:23 ` [RFC, PATCH 08/12] userfaultfd: enable UFFD_FEATURE_MINOR_ANON Kiryl Shutsemau (Meta)
2026-04-14 14:23 ` [RFC, PATCH 09/12] mm/pagemap: add PAGE_IS_UFFD_DEACTIVATED to PAGEMAP_SCAN Kiryl Shutsemau (Meta)
2026-04-14 14:23 ` [RFC, PATCH 10/12] userfaultfd: add UFFDIO_SET_MODE for runtime sync/async toggle Kiryl Shutsemau (Meta)
2026-04-14 14:23 ` [RFC, PATCH 11/12] selftests/mm: add userfaultfd anonymous minor fault tests Kiryl Shutsemau (Meta)
2026-04-14 14:23 ` [RFC, PATCH 12/12] Documentation/userfaultfd: document working set tracking Kiryl Shutsemau (Meta)
2026-04-14 15:28 ` Peter Xu [this message]
2026-04-14 17:08 ` [RFC, PATCH 00/12] userfaultfd: working set tracking for VM guest memory Kiryl Shutsemau
2026-04-14 17:45 ` Peter Xu
2026-04-14 15:37 ` David Hildenbrand (Arm)
2026-04-14 17:10 ` Kiryl Shutsemau
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=ad5dIUpAMs4MuBvV@x1.local \
--to=peterx@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=jthoughton@google.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=pbonzini@redhat.com \
--cc=rppt@kernel.org \
--cc=seanjc@google.com \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=ziy@nvidia.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