Home
last modified time | relevance | path

Searched refs:userfaults (Results 1 – 2 of 2) sorted by relevance

/Linux-v4.19/tools/testing/selftests/vm/
Duserfaultfd.c451 unsigned long userfaults = 0; in uffd_poll_thread() local
491 userfaults++; in uffd_poll_thread()
510 return (void *)userfaults; in uffd_poll_thread()
564 static int stress(unsigned long *userfaults) in stress() argument
570 void **_userfaults = (void **) userfaults; in stress()
891 unsigned long userfaults; in userfaultfd_events_test() local
938 if (pthread_join(uffd_mon, (void **)&userfaults)) in userfaultfd_events_test()
942 printf("userfaults: %ld\n", userfaults); in userfaultfd_events_test()
944 return userfaults != nr_pages; in userfaultfd_events_test()
951 unsigned long userfaults; in userfaultfd_sig_test() local
[all …]
/Linux-v4.19/Documentation/admin-guide/mm/
Duserfaultfd.rst14 For example userfaults allows a proper and more optimal implementation
30 resolve the userfaults it receives via 1) or to manage the virtual
33 The real advantage of userfaults if compared to regular virtual memory
34 management of mremap/mprotect is that the userfaults in all their
44 manager process could handle the userfaults of a multitude of
92 userfaults on the range registered. Not all ioctls will necessarily be
103 The primary ioctl to resolve userfaults is UFFDIO_COPY. That
105 up the blocked userfaults (unless uffdio_copy.mode &
123 just fine in combination with userfaults. Userfaults trigger async
125 aren't waiting for userfaults (i.e. network bound) can keep running in
[all …]