Lines Matching refs:request
555 receive a direct message request originating from any physical core targeting
639 It is possible for an SP to call into another SP through a direct request
820 The request made by an Hypervisor or OS kernel is forwarded to the SPMC and
848 - from Hypervisor or OS kernel to SPMC. The request is relayed by the SPMD.
871 - A VM-to-SP direct request/response shall set the origin world to be non-secure
874 - Similarly, an SP-to-SP direct request/response shall set the FF-A ID bit 15
877 An incoming direct message request arriving at SPMD from NWd is forwarded to
882 An SP sending a direct message request must have bit 15 set in its origin
896 This is a mandatory interface for secure partitions consisting in direct request
899 - An SP can send a direct request to another SP.
900 - An SP can receive a direct request from another SP.
902 - An SP cannot send a direct request to an Hypervisor or OS kernel.
903 - An Hypervisor or OS kernel can send a direct request to an SP.
1029 Using those IDs in source/destination fields of a direct request/response
1032 - SPMC to SPMD direct request/response uses SMC conduit.
1033 - SPMD to SPMC direct request/response uses ERET conduit.
1073 request. When execution on a PE is in the secure state, only a single call chain
1300 request message to SP1. Further, SP1 sends a direct request message to SP2. SP1
1322 - 9) Since SP1 direct request completed with FFA_INTERRUPT, it resumes the
1323 direct request to SP2 by invoking FFA_RUN.
1347 It consists in a SPMD-to-SPMC direct request/response (`SPMC-SPMD direct