Searched refs:granularity (Results 1 – 9 of 9) sorted by relevance
500 (mm->granularity < XLAT_BLOCK_SIZE(level))) in xlat_tables_map_region_action()684 size_t granularity = mm->granularity; in mmap_add_region_check() local693 if ((granularity != XLAT_BLOCK_SIZE(1U)) && in mmap_add_region_check()694 (granularity != XLAT_BLOCK_SIZE(2U)) && in mmap_add_region_check()695 (granularity != XLAT_BLOCK_SIZE(3U))) { in mmap_add_region_check()944 while (mm_cursor->granularity != 0U) { in mmap_add_ctx()
56 while (mm->granularity != 0U) { in mmap_add_alloc_va()
46 mm->granularity); in xlat_mmap_print()
45 .granularity = (_gr), \
147 size_t granularity; member
69 - its mapping granularity (optional).85 The granularity controls the translation table level to go down to when mapping103 then they might enforce a 4KB mapping granularity for this 2MB region from the107 The region's granularity is an optional field; if it is not specified the108 library will choose the mapping granularity for this region as it sees fit (more232 mapping granularity, which leaves the library implementation free to choose233 it. However, in cases where a specific granularity is required, the363 By default [#granularity]_, the algorithm will attempt to minimize the370 requires a finer granularity. Misaligned regions also require a finer371 granularity than what the user may had originally expected, using a lot more[all …]
312 while (mm_cursor->granularity != 0U) { in mmap_add_ctx()
263 achieve a granularity that is smaller than the tab size. For example, with a tab
6528 - Added support to specify the granularity of the mappings of each region, for
