Lines Matching refs:dynamic

26 #. Support for dynamic mapping and unmapping of regions, even while the MMU is
42 support dynamic mapping. Although potential bug fixes will be applied to both
141   Should account for both static and dynamic regions, if applicable.
175 Static and dynamic memory regions
178 The library optionally supports dynamic memory mapping. This feature may be
181 When dynamic memory mapping is enabled, the library categorises mmap regions as
182 *static* or *dynamic*.
190 When the dynamic memory mapping feature is disabled, only static regions exist.
192 The dynamic memory mapping feature may be used to map and unmap transient memory
200 Although this feature provides some level of dynamic memory allocation, this
227 As explained earlier in this document, when the dynamic mapping feature is
228 disabled, there is no notion of dynamic regions. Conceptually, there are only
232 contrast with the dynamic regions APIs (for example
235 Although the definition of static and dynamic regions is not based on the state
244 #. Add some static regions, add some dynamic regions.
316 mmap regions list. Adding a static or dynamic region at this point through one
324 After the ``init_xlat_tables()`` API has been called, only dynamic regions can
360 regions, it must also be applied for dynamic regions to maintain a consistent
373 For example, when the user requests removing a dynamic region, the library
385 TLB invalidation is not required when adding dynamic regions either. Dynamic
387 dynamic mapping request is deemed legitimate, it automatically concerns memory