| /arm-trusted-firmware-2.8.0/docs/threat_model/ |
| A D | threat_model_el3_spm.rst | 55 | DF3 | SPMD to NS forwarding. |
109 - Non-secure endpoint (referred NS-Endpoint later): normal world client at
110 NS-EL2 (Hypervisor) or NS-EL1 (VM or OS kernel).
151 | Threat Agent | NS-Endpoint, S-Endpoint |
189 | Threat Agent | NS-Endpoint, S-Endpoint |
244 | Threat Agent | NS-Endpoint, S-Endpoint |
301 | Threat Agent | NS-Endpoint, S-Endpoint |
343 | Threat Agent | NS-Endpoint, S-Endpoint |
379 | Threat Agent | NS-Endpoint, S-Endpoint |
426 | Threat Agent | NS-Endpoint, S-Endpoint |
[all …]
|
| A D | threat_model_spm.rst | 23 is prevented to map an arbitrary NS physical memory region such as the kernel
75 | ``DF3`` | SPMD to NS forwarding. |
135 - NS-Endpoint identifies a non-secure endpoint: normal world client at NS-EL2
136 (Hypervisor) or NS-EL1 (VM or OS kernel).
176 | ``Threat Agent`` | NS-Endpoint, S-Endpoint |
226 | ``Threat Agent`` | NS-Endpoint, S-Endpoint |
277 | ``Threat Agent`` | NS-Endpoint, S-Endpoint |
347 | ``Threat Agent`` | NS-Endpoint, S-Endpoint |
391 | ``Threat Agent`` | NS-Endpoint, S-Endpoint |
423 | ``Threat Agent`` | NS-Endpoint, S-Endpoint |
[all …]
|
| A D | threat_model_fvp_r.rst | 38 - Any threats regarding NS operation are not relevant.
|
| A D | threat_model.rst | 139 | | world, including NS-EL0 NS-EL1 and NS-EL2 levels |
|
| /arm-trusted-firmware-2.8.0/docs/components/ |
| A D | debugfs-design.rst | 75 non-secure layers, or for which no support exists in the NS side).
81 (`SMC Calling Convention`_), using a specific SiP Function Id. An NS
112 The SMC interface is accessible from an NS environment, that is:
114 - a test payload, bootloader or hypervisor running at NS-EL2
115 - a Linux kernel driver running at NS-EL1
|
| A D | rmm-el3-comms-spec.rst | 15 SMC call from NS.
171 entry from NS Host on receiving an error. This will be done across all the PEs
172 in the system so as to present a symmetric view to the NS Host. Any further
262 results in a world switch to NS. This call is the reply to the original RMI
263 call and it is forwarded by EL3 to the NS world.
278 …err_code,x1,[63:0],RmiCommandReturnCode,Error code returned by the RMI service invoked by NS World…
487 As part of NS world switch, EL3 is expected to maintain a register context
497 As part of SMC forwarding between the NS world and Realm world, EL3 allows x0-x7 to be passed
501 EL3 will always copy x0-x4 from Realm context to NS Context.
513 will not be leaked to the NS Host and to maintain the confidentiality of the Realm World.
[all …]
|
| A D | realm-management-extension.rst | 103 - NS (TF-A Test or Linux),
109 - NS (TF-A Test or Linux),
270 and a suitable NS boot loader is not available, then this option can be used to
|
| A D | secure-partition-manager.rst | 96 - The term Hypervisor refers to the NS-EL2 component managing Virtual Machines
509 the use of two root keys namely S-ROTPK and NS-ROTPK:
512 - BL33 may be signed by the OEM using NS-ROTPK.
513 - An SP may be signed either by SiP (using S-ROTPK) or by OEM (using NS-ROTPK).
515 signed with the NS-ROTPK key.
806 - Hypervisor or OS kernel in NS-EL1/EL2: the SPMD returns the SPMC version
831 SPMC EL2 Stage-1 translation regime and marked as NS buffers in the MMU
1049 NS/S IPA translations. The following controls are set up:
1053 - Stage-2 translations for the NS IPA space access the NS PA space.
1112 - NS-Int: A non-secure physical interrupt. It requires a switch to the normal
[all …]
|
| A D | el3-spmc.rst | 200 The following interfaces are exposed to both NS Client and SPs:
214 The following additional interfaces are forwarded from SPMD to support NS Client:
254 SPMC EL3 translation regime and marked as NS buffers in the MMU
375 - SPMC will set NS Bit to 1 in memory descriptor response.
|
| A D | arm-sip-service.rst | 36 Exception Level (either EL2, or NS EL1 if EL2 isn't implemented) to request to
|
| A D | ras.rst | 203 resulting from errors in NS world, to EL3.
|
| /arm-trusted-firmware-2.8.0/lib/xlat_tables_v2/aarch64/ |
| A D | xlat_tables_arch.c | 71 return LOWER_ATTRS(EL3_S1_NSE | NS); in xlat_arch_get_pas()
77 return LOWER_ATTRS(NS); in xlat_arch_get_pas()
|
| /arm-trusted-firmware-2.8.0/docs/design_documents/ |
| A D | context_mgmt_rework.rst | 55 It is expected that this skip EL2 configuration is only needed for NS
65 modify EL3 sysreg dynamically during the transition between NS and Secure
101 of NS world, the context is allocated by the PSCI lib. This scheme allows TF-A
111 can also export helpers for initialization of NS CPU Context since there is no
123 have some settings which are distinct from NS/S/Realm worlds. In this case,
140 to S-EL2 as SPM can take care of saving the incoming NS EL1 context.
143 world corresponds to the world it came from (eg: if entering EL3 from NS world,
144 the sysregs correspond to the values in NS context). There is a case that EL3
|
| /arm-trusted-firmware-2.8.0/lib/xlat_tables_v2/ |
| A D | xlat_tables_utils.c | 100 switch (desc & LOWER_ATTRS(EL3_S1_NSE | NS)) { in xlat_desc_print()
104 case LOWER_ATTRS(NS): in xlat_desc_print()
114 printf(((LOWER_ATTRS(NS) & desc) != 0ULL) ? "-NS" : "-S"); in xlat_desc_print()
|
| /arm-trusted-firmware-2.8.0/lib/xlat_tables_v2/aarch32/ |
| A D | xlat_tables_arch.c | 53 return LOWER_ATTRS(NS); in xlat_arch_get_pas()
|
| /arm-trusted-firmware-2.8.0/include/lib/xlat_tables/ |
| A D | xlat_tables_defs.h | 144 #define NS (U(0x1) << 3) macro
|
| /arm-trusted-firmware-2.8.0/docs/resources/diagrams/plantuml/ |
| A D | el3_spm_dfd.puml | 24 nsec [label="NS Client"]
|
| A D | spm_dfd.puml | 22 nsec [label="NS Client"]
|
| /arm-trusted-firmware-2.8.0/lib/xlat_tables/ |
| A D | xlat_tables_common.c | 204 desc |= ((attr & MT_NS) != 0U) ? LOWER_ATTRS(NS) : 0U; in mmap_desc()
|
| /arm-trusted-firmware-2.8.0/docs/getting_started/ |
| A D | build-options.rst | 573 Interrupts, resulting from errors in NS world, will be always trapped in
1014 buffer registers from NS ELs when FEAT_BRBE is implemented. BRBE is an
1020 control registers from NS ELs, NS-EL2 or NS-EL1(when NS-EL2 is implemented
1027 registers access from NS ELs, NS-EL2 or NS-EL1 (when NS-EL2 is implemented
1032 access from NS ELs, NS-EL2 or NS-EL1 (when NS-EL2 is implemented but unused),
|
| A D | image-terminology.rst | 154 it's in so it makes sense to encode "NS" in the normal world images. The absence
155 of "NS" implies a secure world image.
|
| A D | psci-lib-integration-guide.rst | 156 for AArch32 and in EL3 for AArch64. The NS bit in SCR (in AArch32) or SCR_EL3
|
| /arm-trusted-firmware-2.8.0/docs/plat/ |
| A D | imx8m.rst | 97 API to get the status and events is called from NS world passing destination
|
| A D | nvidia-tegra.rst | 119 memory controller driver programs this base/size in order to restrict NS
|
| /arm-trusted-firmware-2.8.0/docs/plat/marvell/armada/ |
| A D | build.rst | 171 … in NS world, will be always trapped in TF-A. TF-A in this case enables dirty hack / workaround for
|