mirror of
https://github.com/ARM-software/arm-trusted-firmware.git
synced 2025-04-18 18:44:22 +00:00
![]() When ICH_VMCR_EL2.VBPR1 is written in Secure state (SCR_EL3.NS==0) and then subsequently read in Non-secure state (SCR_EL3.NS==1), a wrong value might be returned. The same issue exists in the opposite way. Adding workaround in EL3 software that performs context save/restore on a change of Security state to use a value of SCR_EL3.NS when accessing ICH_VMCR_EL2 that reflects the Security state that owns the data being saved or restored. For example, EL3 software should set SCR_EL3.NS to 1 when saving or restoring the value ICH_VMCR_EL2 for Non-secure(or Realm) state. EL3 software should clear SCR_EL3.NS to 0 when saving or restoring the value ICH_VMCR_EL2 for Secure state. SDEN documentation: https://developer.arm.com/documentation/SDEN-1775101/latest/ Change-Id: I9f0403601c6346276e925f02eab55908b009d957 Signed-off-by: Govindraj Raja <govindraj.raja@arm.com> |
||
---|---|---|
.. | ||
aarch32 | ||
aarch64 | ||
bl_aux_params | ||
compiler-rt | ||
coreboot | ||
cpus | ||
debugfs | ||
el3_runtime | ||
extensions | ||
fconf | ||
gpt_rme | ||
hob | ||
libc | ||
libfdt | ||
locks | ||
mpmm | ||
optee | ||
pmf | ||
psa | ||
psci | ||
romlib | ||
semihosting | ||
stack_protector | ||
transfer_list | ||
utils | ||
xlat_mpu | ||
xlat_tables | ||
xlat_tables_v2 | ||
zlib |