Jeenu Viswambharan 2ccfcb2ea5 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>		2018-06-21 16:15:23 +01:00
..
sdei_event.c	BL31: Add SDEI dispatcher	2017-11-13 08:38:51 +00:00
sdei_intr_mgmt.c	SDEI: Determine client EL from NS context's SCR_EL3	2018-06-21 16:15:23 +01:00
sdei_main.c	SDEI: Determine client EL from NS context's SCR_EL3	2018-06-21 16:15:23 +01:00
sdei_private.h	SDEI: Determine client EL from NS context's SCR_EL3	2018-06-21 16:15:23 +01:00
sdei_state.c	Remove URLs from comments	2018-02-14 11:41:26 +00:00