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>
1 parent af2c9ec commit 2ccfcb2ea555eb86122e7780010cc50fcee08f54
@Jeenu Viswambharan Jeenu Viswambharan authored on 21 Jun 2018
Showing 3 changed files
View
services/std_svc/sdei/sdei_intr_mgmt.c
View
services/std_svc/sdei/sdei_main.c
View
services/std_svc/sdei/sdei_private.h