Lines Matching refs:userfaultfd

20 Userfaults are delivered and resolved through the ``userfaultfd`` syscall.
22 The ``userfaultfd`` (aside from registering and unregistering virtual
29    registered in the ``userfaultfd`` that allows userland to efficiently
36 ``userfaultfd`` runtime load never takes the mmap_lock for writing).
42 The ``userfaultfd`` once opened by invoking the syscall, can also be
46 (well of course unless they later try to use the ``userfaultfd``
53 When first opened the ``userfaultfd`` must be enabled invoking the
65 defines what memory types are supported by the ``userfaultfd`` and what
68 If the kernel supports registering ``userfaultfd`` ranges on hugetlbfs
71 set if the kernel supports registering ``userfaultfd`` ranges on shared
75 The userland application that wants to use ``userfaultfd`` with hugetlbfs
82 detail below in `Non-cooperative userfaultfd`_ section.
84 Once the ``userfaultfd`` has been enabled the ``UFFDIO_REGISTER`` ioctl should
86 register a memory range in the ``userfaultfd`` by setting the
99 memory from the ``userfaultfd`` registered range). This means a userfault
166 QEMU/KVM is using the ``userfaultfd`` syscall to implement postcopy live
170 ``userfaultfd`` abstraction is generic enough that not a single line of
192 ioctls on the ``userfaultfd`` in order to map the received pages into the
196 poll() to the ``userfaultfd`` in parallel. When a ``POLLIN`` event is
198 the ``userfaultfd`` and receives the fault address (or ``-EAGAIN`` in case the
226 Non-cooperative userfaultfd
229 When the ``userfaultfd`` is monitored by an external manager, the manager
237 	enable ``userfaultfd`` hooks for fork(). When this feature is
238 	enabled, the ``userfaultfd`` context of the parent process is
241 	``userfaultfd`` context in the ``uffd_msg.fork``.
263 ``userfaultfd`` manager. In the former case, the virtual memory is
265 ``userfaultfd``, and if a page fault occurs in that area it will be
270 ``userfaultfd`` context for such area disappears too and the manager will
278 soon as manager executes read(). The ``userfaultfd`` manager should
287 single threaded non-cooperative ``userfaultfd`` manager implementations. A
289 ``userfaultfd`` feature to facilitate multithreading enhancements of the