Subrata Banik | 20fe24b | 2021-12-09 02:46:38 +0530 | [diff] [blame] | 1 | /** @file |
| 2 | DXE SMM Ready To Lock protocol introduced in the PI 1.2 specification. |
| 3 | |
| 4 | According to PI 1.4a specification, this UEFI protocol indicates that |
| 5 | resources and services that should not be used by the third party code |
| 6 | are about to be locked. |
| 7 | This protocol is a mandatory protocol published by PI platform code. |
| 8 | This protocol in tandem with the End of DXE Event facilitates transition |
| 9 | of the platform from the environment where all of the components are |
| 10 | under the authority of the platform manufacturer to the environment where |
| 11 | third party extensible modules such as UEFI drivers and UEFI applications |
| 12 | are executed. The protocol is published immediately after signaling of the |
| 13 | End of DXE Event. PI modules that need to lock or protect their resources |
| 14 | in anticipation of the invocation of 3rd party extensible modules should |
| 15 | register for notification on installation of this protocol and effect the |
| 16 | appropriate protections in their notification handlers. For example, PI |
| 17 | platform code may choose to use notification handler to lock SMM by invoking |
| 18 | EFI_SMM_ACCESS2_PROTOCOL.Lock() function. |
| 19 | |
| 20 | Copyright (c) 2009 - 2017, Intel Corporation. All rights reserved.<BR> |
| 21 | SPDX-License-Identifier: BSD-2-Clause-Patent |
| 22 | |
| 23 | **/ |
| 24 | |
| 25 | #ifndef _DXE_SMM_READY_TO_LOCK_H_ |
| 26 | #define _DXE_SMM_READY_TO_LOCK_H_ |
| 27 | |
| 28 | #include <Protocol/DxeMmReadyToLock.h> |
| 29 | |
| 30 | #define EFI_DXE_SMM_READY_TO_LOCK_PROTOCOL_GUID EFI_DXE_MM_READY_TO_LOCK_PROTOCOL_GUID |
| 31 | |
| 32 | extern EFI_GUID gEfiDxeSmmReadyToLockProtocolGuid; |
| 33 | |
| 34 | #endif |