Manish Pandey 6597fcf169 feat(ras): use FEAT_IESB for error synchronization ... For synchronization of errors at exception boundries TF-A uses "esb" instruction with FEAT_RAS or "dsb" and "isb" otherwise. The problem with esb instruction is, along with synching errors it might also consume the error, which is not ideal in all scenarios. On the other hand we can't use dsb always as its in the hot path. To solve above mentioned problem the best way is to use FEAT_IESB feature which provides controls to insert an implicit Error synchronization event at exception entry and exception return. Assumption in TF-A is, if RAS Extension is present then FEAT_IESB will also be present and enabled. Signed-off-by: Manish Pandey <manish.pandey2@arm.com> Change-Id: Ie5861eec5da4028a116406bb4d1fea7dac232456		2023-11-01 11:11:29 +00:00
..
aarch64	feat(ras): use FEAT_IESB for error synchronization	2023-11-01 11:11:29 +00:00
bl31.ld.S	feat(bl31): reuse SPM_MM specific defines for SPMC_AT_EL3	2023-10-12 10:44:34 +01:00
bl31.mk	fix(mpam): refine MPAM initialization and enablement process	2023-10-25 09:04:29 -05:00
bl31_context_mgmt.c	feat(rme): add context management changes for FEAT_RME	2021-10-05 18:41:35 +02:00
bl31_main.c	refactor(cm): move EL3 registers to global context	2023-10-31 11:18:42 +00:00
bl31_traps.c	feat(el3-runtime): handle traps for IMPDEF registers accesses	2023-04-30 11:04:59 +01:00
ehf.c	refactor(el3-runtime): plat_ic_has_interrupt_type returns bool	2023-09-25 17:09:15 -05:00
interrupt_mgmt.c	refactor(el3-runtime): plat_ic_has_interrupt_type returns bool	2023-09-25 17:09:15 -05:00