Lines Matching refs:faults

10 memory page faults, something otherwise only the kernel code could do.
19 regions of virtual memory with it. Then, any page faults which occur within the
26 1) ``read/POLLIN`` protocol to notify a userland thread of the faults
58 handle kernel page faults have been a useful tool for exploiting the kernel).
63 - Any user can always create a userfaultfd which traps userspace page faults
67 - In order to also trap kernel page faults for the address space, either the
80 to /dev/userfaultfd can always create userfaultfds that trap kernel page faults;
102   other than page faults are supported. These events are described in more
124 bitmask will specify to the kernel which kind of faults to track for
129 hugetlbfs), or all types of intercepted faults.
160 - For ``UFFDIO_REGISTER_MODE_MISSING`` faults, the fault needs to be
166 - For ``UFFDIO_REGISTER_MODE_MINOR`` faults, there is an existing page (in
241 resolving missing / minor faults with ``UFFDIO_COPY`` or ``UFFDIO_CONTINUE``
273 Guest async page faults, ``FOLL_NOWAIT`` and all other ``GUP*`` features work
275 page faults in the guest scheduler so those guest processes that
370 not get further userland page faults from the removed area. Still, the
374 Unlike userland page faults which have to be synchronous and require