docs/components/context-management-library.rst

6 and their accessibility from other components at EL3.
27 to preserve the state of the CPU at the next lower exception level (EL) in a given
32 In a trusted system at any instance, a given CPU could be executing in one of the
70 state called root. EL3 firmware now runs at Root World and thereby is
78 Context Management library running at EL3 should only initialize and monitor the
96 to detect its presence at runtime. This helps dispatchers to select the desired
101 TF-A supports four states for feature enablement at EL3, to make them available
120   existence will be checked at runtime. Default on dynamic platforms (example: FVP).
144    it is essential to know its presence at compile time. Refer to ``ENABLE_FEAT``
285 at compile time as shown below.
292 component found in the Secure and Realm worlds. Instead, the PSCI library at EL3
301 Secure World dispatcher (such as SPMD) at EL3 allocates the memory for ``Secure``
310 Realm World dispatcher (RMMD) at EL3 allocates the memory for ``Realm`` world
340 Later in the cold boot sequence, the BL31 image at EL3 checks for the presence
341 of a Secure world image at S-EL2. If detected, it invokes the secure context
343 the Realm context gets initialized from the RMMD at EL3. Finally, before exiting
352    configurations with TFTF component at NS-EL2.
369 initialized through SPMD at EL3. Upon successful SP initialization, the SPD
386 ``spmd_cpu_on_finish_handler()`` at EL3.
387 The figure above illustrates the same with reference of Primary CPU running at
433 at EL3 to facilitate the saving and restoration of the EL1 system registers
443 at EL3 to facilitate the saving and restoration of the EL2 system registers
538 EL3/Root Context is the execution environment while the CPU is running at EL3.
540 Previously, while the CPU is in execution at EL3, the system registers persist
549 The firmware at EL3 has traditionally operated within the context of the incoming
557 features for its own execution at EL3.
566 architectural features at EL3. Its a simple restore operation ``setup_el3_execution_context``
581 EL3 execution context needs to setup at both boot time (cold and warm boot)
582 entrypaths and at all the possible exception handlers routing to EL3 at runtime.