Lines Matching full:mappings

25  * and unmap memory. Mappings may be flagged as sparse. Sparse mappings are not
29  * Userspace may request memory backed mappings either within or outside of the
31  * mapping. Subsequently requested memory backed mappings within a sparse
33  * mapping. If such memory backed mappings are unmapped the kernel will make
35  * Requests to unmap a sparse mapping that still contains memory backed mappings
36  * will result in those memory backed mappings being unmapped first.
38  * Unmap requests are not bound to the range of existing mappings and can even
39  * overlap the bounds of sparse mappings. For such a request the kernel will
40  * make sure to unmap all memory backed mappings within the given range,
41  * splitting up memory backed mappings which are only partially contained
46  * backed mappings being mapped and unmapped, either within a single or multiple
47  * VM_BIND ioctl calls, there are some restrictions for sparse mappings.
50  *   - unmap non-existent sparse mappings
53  *   - unmap a sparse mapping and map new memory backed mappings overlapping the
59  * mappings are created in the GPU's MMU. If the given memory is swapped out
61  * details into it's internal alloctor and create the actual MMU mappings once
64  * mappings, as requested by userspace previously, are actually mapped once the
81  * an up to date view of the VA space. However, the actual mappings might still