Searched hist:"2 ccfcb2ea555eb86122e7780010cc50fcee08f54" (Results 1 – 3 of 3) sorted by relevance
| /rk3399_ARM-atf/services/std_svc/sdei/ |
| H A D | sdei_private.h | a8778dd53ce3b44204b1ef7f12a0f2ec39d3980a Fri Jun 22 11:00:20 UTC 2018 Jeenu Viswambharan <jeenu.viswambharan@arm.com> SDEI: Fix determining client EL
commit 2ccfcb2ea555eb86122e7780010cc50fcee08f54 ("SDEI: Determine client
EL from NS context's SCR_EL3") intended to read from SCR_EL3, but
wrongly read from SPSR_EL3 instead. This patch fixes that.
Change-Id: I8ffea39cc98ef59cb8e7a4c6ef4cb12011c58536
Signed-off-by: Jeenu Viswambharan <jeenu.viswambharan@arm.com>
2ccfcb2ea555eb86122e7780010cc50fcee08f54 Thu Jun 21 07:47:42 UTC 2018 Jeenu Viswambharan <jeenu.viswambharan@arm.com> 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>
|
| H A D | sdei_main.c | 2ccfcb2ea555eb86122e7780010cc50fcee08f54 Thu Jun 21 07:47:42 UTC 2018 Jeenu Viswambharan <jeenu.viswambharan@arm.com> 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>
|
| H A D | sdei_intr_mgmt.c | 2ccfcb2ea555eb86122e7780010cc50fcee08f54 Thu Jun 21 07:47:42 UTC 2018 Jeenu Viswambharan <jeenu.viswambharan@arm.com> 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>
|