Lines Matching refs:mapping

19 #. Support for dynamic mapping and unmapping of regions, even while the MMU is
35 support dynamic mapping. ``lib/xlat_mpu``, which configures Arm's MPU
69 - its mapping granularity (optional).
85 The granularity controls the translation table level to go down to when mapping
92   contains 512 entries, each mapping 4KB).
103 then they might enforce a 4KB mapping granularity for this 2MB region from the
108 library will choose the mapping granularity for this region as it sees fit (more
109 details can be found in `The memory mapping algorithm`_ section below).
187 The library optionally supports dynamic memory mapping. This feature may be
190 When dynamic memory mapping is enabled, the library categorises mmap regions as
199 When the dynamic memory mapping feature is disabled, only static regions exist.
201 The dynamic memory mapping feature may be used to map and unmap transient memory
212 the limits of these allocations ; the library will deny any mapping request that
232 mapping granularity, which leaves the library implementation free to choose
237 As explained earlier in this document, when the dynamic mapping feature is
300   translation tables contexts and mapping/unmapping memory regions. This module
356 The memory mapping algorithm
359 The mapping function is implemented as a recursive algorithm. It is however
365 favour mapping a region using the biggest possible blocks, only creating a
369 The most common reason for needing a sub-table is when a specific mapping
394 This mapping algorithm does not apply to the MPU library, since the MPU hardware
420 dynamic mapping request is deemed legitimate, it automatically concerns memory
425 mapping cannot be cached in the TLBs.
429 .. [#granularity] That is, when mmap regions do not enforce their mapping