-/**\r
- Lets the caller get one distinct application processor (AP) in the enabled processor pool to execite a \r
- caller-provided code stream while in SMM. \r
-\r
- @param Procedure A pointer to the code stream to be run on the designated AP of the system.\r
- @param CpuNumber The zero-based index of the processor number of the AP on which the code stream is\r
- supposed to run. If the processor number points to the current processor or a disabled\r
- processor, then it will not run the supplied code.\r
- @param ProcArguments Allows the caller to pass a list of parameters to the code that is run by\r
- the AP. It is an optional common mailbox between APs and the BSP to share information.\r
-\r
- @retval EFI_SUCCESS The call was successful and the return parameters are valid.\r
- @retval EFI_INVALID_PARAMETER The input arguments are out of range.\r
- @retval EFI_INVALID_PARAMETER The CPU requested is not available on this SMI invocation.\r
- @retval EFI_INVALID_PARAMETER The CPU cannot support an additional service invocation.\r
- \r
- @note: Inconsistent with specification here:\r
- In Framework Spec, this definition does not exist. This method is introduced in PI1.0 spec for \r
- implementation needs.\r
- \r
-**/\r
-typedef\r
-EFI_STATUS\r
-(EFIAPI *EFI_SMM_STARTUP_THIS_AP)(\r
- IN FRAMEWORK_EFI_AP_PROCEDURE Procedure,\r
- IN UINTN CpuNumber,\r
- IN OUT VOID *ProcArguments OPTIONAL\r
- );\r
-\r