Lines Matching refs:preempted

122    software is in control of how its execution is preempted by non-secure
148    in Secure-EL1/Secure-EL0 is in control of how its execution is preempted
562    service which indicates that the SP execution has been preempted by a
730    that SP execution can be preempted while handling an interrupt by a
774    ``TSP_HANDLE_SEL1_INTR_AND_RETURN``. If the TSP was preempted earlier by a non
808    the secure CPU context (see step 3 above) in case the TSP had been preempted
823 The TSP in Secure-EL1 can be preempted by a non-secure interrupt during
830 It should be noted that while TSP is preempted, the TSPD only allows entry into
831 the TSP either for Secure-EL1 interrupt handling or for resuming the preempted
833 (See Section `Implication of preempted SMC on Non-Secure Software`_).
878 (see section `Implication of preempted SMC on Non-Secure Software`_).  The TSPD
885 #. Checks whether the TSP needs a resume i.e check if it was preempted. It
943    that means that a higher priority interrupt has preempted it. Invoke
972 Implication of preempted SMC on Non-Secure Software
975 A ``yielding`` SMC call to Secure payload can be preempted by a non-secure
979 must return back to the secure payload to resume the preempted SMC call.
981 preempted SMC.
983 A ``fast`` SMC cannot be preempted and hence this case will not happen for
988 ``yielding`` SMC which means it too can be be preempted. The typical non
998     while (rc == SMC_PREEMPTED) {       /* Check if the SMC call is preempted */
1007 preempted. If it is, then the resume SMC call ``TSP_FID_RESUME`` is issued. The
1008 return value of the SMC call is tested again to check if it is preempted.
1010 SMC is preempted, until it is resumed using ``TSP_FID_RESUME`` SMC and