Lines Matching refs:mapping

19 #. Support for dynamic mapping and unmapping of regions, even while the MMU is
35 support dynamic mapping. Although potential bug fixes will be applied to both
63 - its mapping granularity (optional).
79 The granularity controls the translation table level to go down to when mapping
86   contains 512 entries, each mapping 4KB).
97 then they might enforce a 4KB mapping granularity for this 2MB region from the
102 library will choose the mapping granularity for this region as it sees fit (more
103 details can be found in `The memory mapping algorithm`_ section below).
171 The library optionally supports dynamic memory mapping. This feature may be
174 When dynamic memory mapping is enabled, the library categorises mmap regions as
183 When the dynamic memory mapping feature is disabled, only static regions exist.
185 The dynamic memory mapping feature may be used to map and unmap transient memory
196 the limits of these allocations ; the library will deny any mapping request that
216 mapping granularity, which leaves the library implementation free to choose
220 As explained earlier in this document, when the dynamic mapping feature is
283   translation tables contexts and mapping/unmapping memory regions. This module
339 The memory mapping algorithm
342 The mapping function is implemented as a recursive algorithm. It is however
348 favour mapping a region using the biggest possible blocks, only creating a
352 The most common reason for needing a sub-table is when a specific mapping
395 dynamic mapping request is deemed legitimate, it automatically concerns memory
400 mapping cannot be cached in the TLBs.
404 .. [#granularity] That is, when mmap regions do not enforce their mapping