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