Lines Matching full:tables

1 Translation (XLAT) Tables Library
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
51 translation tables library.
68 library transpose that in a set of translation tables. As a result, the library
69 might create new translation tables, update or split existing ones.
88 The first solution potentially requires less translation tables, hence
91 page tables to refine the mappings. If a single level-2 entry has been used
108 The library can create or modify translation tables pertaining to a different
111 create translation tables pertaining to the S-EL1&0 translation regime.
115 the status of a set of translation tables for a given translation regime.
136 * The number of sub-translation tables to allocate.
138   Number of translation tables to statically allocate for this context,
141   specify the number of level-2 and level-3 translation tables to pre-allocate
161 - number of sub-translation tables: ``MAX_XLAT_TABLES``;
178   added early on, before the translation tables are created and populated. They
239 #. Initialize translation tables based on the list of mmap regions (using one of
283   translation tables contexts and mapping/unmapping memory regions. This module
285   the translation tables context affected by them.
301   translation tables and helpers to query memory attributes and to modify them.
314 From mmap regions to translation tables
324 tables to program into the MMU.
328 of the ``mmap_add*()`` APIs does not affect the translation tables in any way,
330 user calls the ``init_xlat_tables()`` that the translation tables are populated
332 optimization that allows creation of the initial set of translation tables in
336 be added. Changes to the translation tables (as well as the mmap regions list)
343 bound by the level of depth of the translation tables (the Armv8-A architecture
347 number of translation tables created to satisfy the user's request. It will
359 aligned to 2 MiB then additional level 3 tables are also needed.
365 instead, as well as additional tables at the next level.
373 entries in the translation tables are checked to ensure consistency. Please
386 A counter-example is the initialization of translation tables. In this case,