Lines Matching refs:OS
115 (Hypervisor or OS kernel) to the SPMC.
353 Secure Payload BL32 (Trusted OS): offset=0x1BCD1, size=0x15270, cmdline="--tos-fw"
470 or the SPMC itself, the OS Kernel/Hypervisor, or other NWd VMs. The SPMC
538 secure partitions. For this a VM (Hypervisor or OS kernel), or SP invokes one of:
720 deployed in NWd, the Hypervisor or OS kernel must invoke the interface
813 - Hypervisor or OS kernel in NS-EL1/EL2: the SPMD returns the SPMC version
827 The request made by an Hypervisor or OS kernel is forwarded to the SPMC and
837 When invoked from the Hypervisor or OS kernel, the buffers are mapped into the
846 caller, either it being the Hypervisor or OS kernel, as well as a secure
855 - from Hypervisor or OS kernel to SPMC. The request is relayed by the SPMD.
909 - An SP cannot send a direct request to an Hypervisor or OS kernel.
910 - An Hypervisor or OS kernel can send a direct request to an SP.
911 - An SP can send a direct response to an Hypervisor or OS kernel.
920 normal world. Hence, the Hypervisor or OS kernel must use both ABIs for SPMC
969 The Hypervisor or OS kernel can issue the FFA_SPM_ID_GET call handled by the
1080 or OS kernel has the possibility to rely on the SPMC to maintain the state
1368 triggers while execution is in secure world. We assume OS kernel sends a direct
1420 - The Hypervisor or OS kernel is the component initiating PSCI service calls.
1588 Trusted OS functionality. It is also useful to reduce jitter and cycle