Searched refs:pagefault (Results 1 – 16 of 16) sorted by relevance
/Linux-v6.6/tools/testing/selftests/mm/ |
D | uffd-common.c | 431 if (msg->arg.pagefault.flags & UFFD_PAGEFAULT_FLAG_WP) { in uffd_handle_page_fault() 433 wp_range(uffd, msg->arg.pagefault.address, page_size, false); in uffd_handle_page_fault() 435 } else if (msg->arg.pagefault.flags & UFFD_PAGEFAULT_FLAG_MINOR) { in uffd_handle_page_fault() 452 ((char *)msg->arg.pagefault.address - in uffd_handle_page_fault() 456 continue_range(uffd, msg->arg.pagefault.address, page_size, in uffd_handle_page_fault() 481 if (msg->arg.pagefault.flags & UFFD_PAGEFAULT_FLAG_WRITE) in uffd_handle_page_fault() 484 offset = (char *)(unsigned long)msg->arg.pagefault.address - area_dst; in uffd_handle_page_fault()
|
D | uffd-unit-tests.c | 993 if (msg->arg.pagefault.flags & in uffd_poison_handle_fault() 995 err("unexpected fault type %llu", msg->arg.pagefault.flags); in uffd_poison_handle_fault() 997 offset = (char *)(unsigned long)msg->arg.pagefault.address - area_dst; in uffd_poison_handle_fault()
|
/Linux-v6.6/tools/testing/selftests/powerpc/tm/ |
D | Makefile | 8 tm-signal-context-force-tm tm-poison tm-signal-pagefault 27 $(OUTPUT)/tm-signal-pagefault: CFLAGS += -pthread -m64
|
D | .gitignore | 17 tm-signal-pagefault
|
D | tm-signal-pagefault.c | 122 uffdio_copy.dst = msg.arg.pagefault.address & ~(pagesize-1); in fault_handler_thread()
|
/Linux-v6.6/Documentation/fb/ |
D | deferred_io.rst | 6 buffer and the MMU pagefault as a pretrigger for when to perform the device 13 - we get pagefault and reach fault handler 23 - get pagefault and the above sequence occurs again
|
/Linux-v6.6/Documentation/gpu/rfc/ |
D | i915_gem_lmem.rst | 17 * Use TTM CPU pagefault handler
|
/Linux-v6.6/fs/ |
D | userfaultfd.c | 169 if (len && (start > uwq->msg.arg.pagefault.address || in userfaultfd_wake_function() 170 start + len <= uwq->msg.arg.pagefault.address)) in userfaultfd_wake_function() 251 msg.arg.pagefault.address = (features & UFFD_FEATURE_EXACT_ADDRESS) ? in userfault_msg() 264 msg.arg.pagefault.flags |= UFFD_PAGEFAULT_FLAG_WRITE; in userfault_msg() 266 msg.arg.pagefault.flags |= UFFD_PAGEFAULT_FLAG_WP; in userfault_msg() 268 msg.arg.pagefault.flags |= UFFD_PAGEFAULT_FLAG_MINOR; in userfault_msg() 270 msg.arg.pagefault.feat.ptid = task_pid_vnr(current); in userfault_msg()
|
/Linux-v6.6/include/uapi/linux/ |
D | userfaultfd.h | 116 } pagefault; member
|
/Linux-v6.6/tools/testing/selftests/kvm/ |
D | demand_paging_test.c | 64 uint64_t addr = msg->arg.pagefault.address; in handle_uffd_page_request()
|
/Linux-v6.6/drivers/gpu/drm/i915/ |
D | Kconfig.profile | 32 userspace GGTT mmaps and force userspace to take a pagefault on
|
/Linux-v6.6/tools/testing/selftests/kvm/aarch64/ |
D | page_fault_test.c | 313 uint64_t addr = msg->arg.pagefault.address; in uffd_generic_handler() 314 uint64_t flags = msg->arg.pagefault.flags; in uffd_generic_handler()
|
/Linux-v6.6/tools/testing/selftests/x86/ |
D | test_shadow_stack.c | 470 req.dst = msg.arg.pagefault.address; in uffd_thread()
|
/Linux-v6.6/Documentation/admin-guide/mm/ |
D | userfaultfd.rst | 175 ``pagefault.flags`` within the ``uffd_msg``, checking for the 206 ``msg.arg.pagefault.flags & UFFD_PAGEFAULT_FLAG_WP`` set. Now you send 208 again while ``pagefault.mode`` does not have ``UFFDIO_WRITEPROTECT_MODE_WP``
|
/Linux-v6.6/tools/perf/Documentation/ |
D | perf-trace.txt | 280 As you can see, there was major pagefault in python process, from
|
/Linux-v6.6/Documentation/filesystems/ |
D | fuse.rst | 390 but is caused by a pagefault. ::
|