Lines Matching +full:total +full:- +full:timeout
6 - Retrieving information of multi-processor environment and MP-related status of
8 - Dispatching user-provided function to APs.
9 - Maintain MP-related processor status.
16 MP Services Protocol is hardware-independent. Most of the logic of this protocol
17 is architecturally neutral. It abstracts the multi-processor environment and
25 MP Services Protocol may be used by non-CPU DXE drivers to speed up platform boot
28 Diagnostics applications may also use this protocol for multi-processor.
30 Copyright (c) 2006 - 2017, Intel Corporation. All rights reserved.<BR>
31 SPDX-License-Identifier: BSD-2-Clause-Patent
91 /// Zero-based physical package number that identifies the cartridge of the processor.
95 /// Zero-based physical core number within package of the processor.
99 /// Zero-based logical thread number within core of the processor.
105 /// Structure that defines the 6-level physical location of the processor
109 …/// Package Zero-based physical package number that identifies the cartridge of the process…
113 /// Module Zero-based physical module number within package of the processor.
117 /// Tile Zero-based physical tile number within module of the processor.
121 /// Die Zero-based physical die number within tile of the processor.
125 /// Core Zero-based physical core number within die of the processor.
129 /// Thread Zero-based logical thread number within core of the processor.
135 /// The 6-level physical location of the processor, including the
191 - The number of logical processors that are present in the system.
192 - The number of enabled logical processors in the system at the instant
201 EFI_INVALID_PARAMETER is returned. Otherwise, the total number of processors
207 @param[out] NumberOfProcessors Pointer to the total number of logical
230 Gets detailed MP-related information on the requested processor at the
233 This service retrieves detailed MP-related information about any processor
235 - The processor information may change during the course of a boot session.
236 - The information presented here is entirely MP related.
239 slot numbers is all considered platform-related information and is not provided
266 both blocking and non-blocking requests. The non-blocking requests use EFI
279 APs finish or TimeoutInMicroSecs expires. Otherwise, execution is in non-blocking
281 non-blocking mode is requested after the UEFI Event EFI_EVENT_GROUP_READY_TO_BOOT
284 If the timeout specified by TimeoutInMicroseconds expires before all APs return
294 that the Procedure function is MP-safe. Hence, the tasks that can be run in
295 parallel are limited to certain independent tasks and well-controlled exclusive
302 In non-blocking execution mode, BSP is freed to return to the caller and then
304 sequence needs to occur in a non-blocking execution mode:
306 -# The caller that intends to use this MP Services Protocol in non-blocking
309 is not NULL, then StartupAllAPs() executes in non-blocking mode. It requests
312 -# The caller can use the CheckEvent() and WaitForEvent() services to check
314 -# When the APs complete their task or TimeoutInMicroSecondss expires, the MP
317 signaled. If all APs returned from Procedure prior to the timeout, then
319 the timeout, then FailedCpuList is filled in with the list of the failed
322 -# This invocation of SignalEvent() function informs the caller that invoked
324 the specified task or a timeout occurred. The contents of FailedCpuList
326 prior to the timeout.
343 not NULL, then execute in non-blocking mode.
356 blocking or non-blocking mode. Zero means
357 infinity. If the timeout expires before
363 If the timeout expires in blocking mode,
364 BSP returns EFI_TIMEOUT. If the timeout
365 expires in non-blocking mode, WaitEvent
372 finish before timeout expires, then its
379 when the call returns. In non-blocking mode,
385 the timeout expired.
386 @retval EFI_SUCCESS In non-blocking mode, function has been dispatched
388 @retval EFI_UNSUPPORTED A non-blocking mode request was made after the
394 @retval EFI_TIMEOUT In blocking mode, the timeout expired before
412 This service lets the caller get one enabled AP to execute a caller-provided
415 See EFI_MP_SERVICES_PROTOCOL.StartupAllAPs() for more details on non-blocking
421 TimeoutInMicroSecondss expires. Otherwise, execution is in non-blocking mode.
422 BSP proceeds to the next task without waiting for the AP. If a non-blocking mode
426 If the timeout specified by TimeoutInMicroseconds expires before the AP returns
437 from 0 to the total number of logical
438 processors minus 1. The total number of
445 not NULL, then execute in non-blocking mode.
458 blocking or non-blocking mode. Zero means
459 infinity. If the timeout expires before
465 If the timeout expires in blocking mode,
466 BSP returns EFI_TIMEOUT. If the timeout
467 expires in non-blocking mode, WaitEvent
473 In non-blocking mode, if AP returns from
474 Procedure before the timeout expires, its
481 the timeout expires.
482 @retval EFI_SUCCESS In non-blocking mode, the function has been
484 @retval EFI_UNSUPPORTED A non-blocking mode request was made after the
488 @retval EFI_TIMEOUT In blocking mode, the timeout expired before
525 BSP. The range is from 0 to the total number of
526 logical processors minus 1. The total number of
569 The range is from 0 to the total number of
570 logical processors minus 1. The total number of
607 The returned value is in the range from 0 to the total number of logical
608 processors minus 1. The total number of logical processors can be retrieved
616 The range is from 0 to the total number of
617 logical processors minus 1. The total number of
649 /// guarantee that all non-blocking mode requests on all APs have been completed
653 /// be used to guarantee that APs have completed their non-blocking mode requests.
656 /// and StartupThisAp() services must no longer support non-blocking mode requests.