Lines Matching refs:tables

4 This document describes the design of the translation tables library (version 2)
6 tables based on a description of the memory layout, as well as setting up system
12 #. Statically allocate translation tables and populate them (at run-time) based
16 #. Support for generating translation tables pertaining to a different
57 translation tables library.
74 library transpose that in a set of translation tables. As a result, the library
75 might create new translation tables, update or split existing ones.
94 The first solution potentially requires less translation tables, hence
97 page tables to refine the mappings. If a single level-2 entry has been used
115 timing, the MPU hardware does not involve memory-resident translation tables.
124 The library can create or modify translation tables pertaining to a different
127 create translation tables pertaining to the S-EL1&0 translation regime.
131 the status of a set of translation tables for a given translation regime.
152 * The number of sub-translation tables to allocate.
154   Number of translation tables to statically allocate for this context,
157   specify the number of level-2 and level-3 translation tables to pre-allocate
177 - number of sub-translation tables: ``MAX_XLAT_TABLES``;
194   added early on, before the translation tables are created and populated. They
256 #. Initialize translation tables based on the list of mmap regions (using one of
300   translation tables contexts and mapping/unmapping memory regions. This module
302   the translation tables context affected by them.
318   translation tables and helpers to query memory attributes and to modify them.
331 From mmap regions to translation tables
341 tables to program into the MMU.
345 of the ``mmap_add*()`` APIs does not affect the translation tables in any way,
347 user calls the ``init_xlat_tables()`` that the translation tables are populated
349 optimization that allows creation of the initial set of translation tables in
353 be added. Changes to the translation tables (as well as the mmap regions list)
360 bound by the level of depth of the translation tables (the Armv8-A architecture
364 number of translation tables created to satisfy the user's request. It will
376 aligned to 2 MiB then additional level 3 tables are also needed.
382 instead, as well as additional tables at the next level.
390 entries in the translation tables are checked to ensure consistency. Please
406 A counter-example is the initialization of translation tables. In this case,