Searched refs:FOLL_GET (Results 1 – 6 of 6) sorted by relevance
| /linux-6.15/Documentation/core-api/ |
| H A D | pin_user_pages.rst | 39 FOLL_PIN and FOLL_GET are mutually exclusive for a given gup call. However, 41 FOLL_PIN and FOLL_GET. It's just the call site that needs to choose one or the 44 The FOLL_PIN implementation is nearly the same as FOLL_GET, except that FOLL_PIN 77 For these get_user_pages*() functions, FOLL_GET might not even be specified. 78 Behavior is a little more complex than above. If FOLL_GET was *not* specified, 80 sets FOLL_GET for you, and proceeds to pin pages by incrementing the refcount 125 FOLL_PIN, FOLL_GET, FOLL_LONGTERM: when to use which flags 194 INCORRECT (uses FOLL_GET calls): 216 Another way of thinking about FOLL_GET, FOLL_PIN, and FOLL_LONGTERM 220 FOLL_GET is for struct page manipulation, without affecting the data that the [all …]
|
| /linux-6.15/mm/ |
| H A D | gup.c | 153 if (flags & FOLL_GET) in try_grab_folio() 537 if (WARN_ON_ONCE((flags & (FOLL_GET | FOLL_PIN)) == 0)) in try_grab_folio_fast() 543 if (flags & FOLL_GET) in try_grab_folio_fast() 691 if (!(flags & (FOLL_GET | FOLL_PIN))) in follow_huge_pud() 848 if (WARN_ON_ONCE((flags & (FOLL_PIN | FOLL_GET)) == in follow_page_pte() 849 (FOLL_PIN | FOLL_GET))) in follow_page_pte() 1753 flags |= FOLL_GET; in __get_user_pages_locked() 2276 FOLL_FORCE | FOLL_DUMP | FOLL_GET); in get_dump_page() 2573 (FOLL_PIN | FOLL_GET))) in is_valid_gup_args() 3392 FOLL_FORCE | FOLL_PIN | FOLL_GET | in gup_fast_fallback() [all …]
|
| H A D | rmap.c | 2681 FOLL_GET | FOLL_WRITE | FOLL_SPLIT_PMD, in make_device_exclusive()
|
| H A D | huge_memory.c | 1674 if (!(flags & (FOLL_GET | FOLL_PIN))) in follow_devmap_pmd()
|
| /linux-6.15/include/linux/ |
| H A D | mm_types.h | 1631 FOLL_GET = 1 << 1, enumerator
|
| /linux-6.15/drivers/virt/nitro_enclaves/ |
| H A D | ne_misc_dev.c | 967 ne_mem_region->pages + i, FOLL_GET); in ne_set_user_memory_region_ioctl()
|