Lines Matching refs:region
62 An ``mmap_region`` is an abstract, concise way to represent a memory region to
77 The region attributes specify the type of memory (for example device or cached
80 the EL1&0 translation regime, the attributes also specify whether the region is
81 a User region (EL0) or Privileged region (EL1). See the ``MT_xxx`` definitions
86 the region. For example, assuming the MMU has been configured to use a 4KB
87 granule size, the library might map a 2MB memory region using either of the two
95 potentially less memory. However, if part of this 2MB region is later remapped
103 then they might enforce a 4KB mapping granularity for this 2MB region from the
107 The region's granularity is an optional field; if it is not specified the
108 library will choose the mapping granularity for this region as it sees fit (more
204 example, a memory region that is only required at boot time while the system is
270 Nonetheless, these APIs will check upfront whether the region can be
273 the new region will overlap another one in an invalid way, or if any other
277 without adding the offending memory region.
336 is a request to map (resp. unmap) a memory region, it is added to (resp. removed
344 mmap regions list. Adding a static or dynamic region at this point through one
346 they only get registered in the internal mmap region list. It is only when the
365 favour mapping a region using the biggest possible blocks, only creating a
389 order of all regions at all times. As each new region is mapped, existing
401 For example, when the user requests removing a dynamic region, the library
402 invalidates all TLB entries associated to that region to ensure that these
419 regions are not allowed to overlap existing memory region. Therefore, if the