Lines Matching +full:multi +full:- +full:processors
6 - Retrieving information of multi-processor environment and MP-related status of
7 specific processors.
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
18 status of processors, and provides interfaces to retrieve information, maintain,
23 MP Services Protocol may also be used to program and configure processors, such
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
187 and the number of those logical processors that are enabled on this boot.
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
195 Because MP Service Protocol provides services to enable and disable processors
196 dynamically, the number of enabled logical processors may vary during the
201 EFI_INVALID_PARAMETER is returned. Otherwise, the total number of processors
208 processors in the system, including the BSP
211 processors that exist in system, including
214 @retval EFI_SUCCESS The number of logical processors and enabled
215 logical processors was retrieved.
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
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
322 -# This invocation of SignalEvent() function informs the caller that invoked
343 not NULL, then execute in non-blocking mode.
356 blocking or non-blocking mode. Zero means
365 expires in non-blocking mode, WaitEvent
379 when the call returns. In non-blocking mode,
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
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
438 processors minus 1. The total number of
439 logical processors can be retrieved by
445 not NULL, then execute in non-blocking mode.
458 blocking or non-blocking mode. Zero means
467 expires in non-blocking mode, WaitEvent
473 In non-blocking mode, if AP returns from
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
526 logical processors minus 1. The total number of
527 logical processors can be retrieved by
570 logical processors minus 1. The total number of
571 logical processors can be retrieved by
608 processors minus 1. The total number of logical processors can be retrieved
611 is returned. Otherwise, the current processors handle number is returned in
617 logical processors minus 1. The total number of
618 logical processors can be retrieved by
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.