aboutsummaryrefslogtreecommitdiff
path: root/bl31
diff options
context:
space:
mode:
authorJeenu Viswambharan <jeenu.viswambharan@arm.com>2018-06-21 08:47:42 +0100
committerJeenu Viswambharan <jeenu.viswambharan@arm.com>2018-06-21 16:15:23 +0100
commit2ccfcb2ea555eb86122e7780010cc50fcee08f54 (patch)
treede6c36318b61877f08288f3b911f1ab1c04ef209 /bl31
parentaf2c9ecdf1b68c6243f6d23e26d0281d182d3b45 (diff)
downloadtrusted-firmware-a-2ccfcb2ea555eb86122e7780010cc50fcee08f54.tar.gz
SDEI: Determine client EL from NS context's SCR_EL3
Currently, the dispatcher reads from SCR_EL3 register directly to determine the EL of SDEI client. This is with the assumption that SCR_EL3 is not modified throughout. However, with RAS work flows, it's possible that SCR_EL3 register contains values corresponding to Secure world, and therefore EL determination can go wrong. To mitigate this, always read the register from the saved Non-secure context. Change-Id: Ic85e4021deb18eb58757f676f9a001174998543a Signed-off-by: Jeenu Viswambharan <jeenu.viswambharan@arm.com>
Diffstat (limited to 'bl31')
0 files changed, 0 insertions, 0 deletions