refactor(interrupts): changes based on updated guidance
In anticipation of updated guidance for interrupt management based
on FF-A v1.1 EAC0 specification, changes are made to add helper
utilities to distinguish handling secure interrupt triggered while
executing in normal world vs secure world.
Moreover, a legacy design constraint has been removed. SPMC now
changes the state of the target SP to RUNNING upon resuming it
for handling a secure virtual interrupt.
Change-Id: I4de5ec8c92e55238be9f43a8ea99bda39b0f9c8d
Signed-off-by: Madhukar Pappireddy <madhukar.pappireddy@arm.com>
diff --git a/src/arch/aarch64/hypervisor/handler.c b/src/arch/aarch64/hypervisor/handler.c
index 0d46b66..68a1777 100644
--- a/src/arch/aarch64/hypervisor/handler.c
+++ b/src/arch/aarch64/hypervisor/handler.c
@@ -635,7 +635,7 @@
*args = api_ffa_notification_info_get(current);
return true;
case FFA_INTERRUPT_32:
- *args = plat_ffa_delegate_ffa_interrupt(current, next);
+ *args = plat_ffa_handle_secure_interrupt(current, next, true);
return true;
case FFA_CONSOLE_LOG_32:
case FFA_CONSOLE_LOG_64:
@@ -985,7 +985,7 @@
#if SECURE_WORLD == 1
struct vcpu *next = NULL;
- plat_ffa_secure_interrupt(current(), &next);
+ plat_ffa_handle_secure_interrupt(current(), &next, false);
/*
* Since we are in interrupt context, set the bit for the