Lines Matching +full:vs +full:- +full:supply

10 Userfaults allow the implementation of on-demand paging from userland
38 Vmas are not suitable for page- (or hugepage) granular fault tracking
48 is a corner case that would currently return ``-EBUSY``).
82 detail below in `Non-cooperative userfaultfd`_ section.
94 memory backend (anonymous memory vs tmpfs vs real filebacked
101 user-faulted page.
113 - If you requested ``UFFDIO_REGISTER_MODE_MISSING`` when registering then
119 - None of the page-delivering ioctls default to the range that you
123 - You get the address of the access that triggered the missing page
125   uffd.  You can supply as many pages as you want with ``UFFDIO_COPY`` or
129 - Be sure to test for all errors including
134 ---------------------------
156 which you supply a page and undo write protect.  Note that there is a
160 you still need to supply a page when ``UFFDIO_REGISTER_MODE_MISSING`` was
198 the ``userfaultfd`` and receives the fault address (or ``-EAGAIN`` in case the
215 doesn't need to keep any per-page state bitmap relative to the live
216 migration around and a single per-page bitmap has to be maintained in
226 Non-cooperative userfaultfd
245 	non-cooperative process moves a virtual memory area to a
277 asynchronously and the non-cooperative process resumes execution as
281 return ``-ENOSPC`` when the monitored process exits at the time of
282 ``UFFDIO_COPY``, and ``-ENOENT``, when the non-cooperative process has changed
287 single threaded non-cooperative ``userfaultfd`` manager implementations. A