]>
Commit | Line | Data |
---|---|---|
688b2cad AB |
1 | /** @file\r |
2 | \r | |
3 | Parts of the SMM/MM implementation that are specific to standalone MM\r | |
4 | \r | |
5 | Copyright (c) 2011 - 2018, Intel Corporation. All rights reserved. <BR>\r | |
6 | Copyright (c) 2018, Linaro, Ltd. All rights reserved. <BR>\r | |
7 | This program and the accompanying materials\r | |
8 | are licensed and made available under the terms and conditions of the BSD License\r | |
9 | which accompanies this distribution. The full text of the license may be found at\r | |
10 | http://opensource.org/licenses/bsd-license.php\r | |
11 | \r | |
12 | THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS,\r | |
13 | WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED.\r | |
14 | \r | |
15 | **/\r | |
16 | \r | |
17 | #include "Variable.h"\r | |
18 | \r | |
19 | /**\r | |
20 | This function checks if the buffer is valid per processor architecture and\r | |
21 | does not overlap with SMRAM.\r | |
22 | \r | |
23 | @param Buffer The buffer start address to be checked.\r | |
24 | @param Length The buffer length to be checked.\r | |
25 | \r | |
26 | @retval TRUE This buffer is valid per processor architecture and does not\r | |
27 | overlap with SMRAM.\r | |
28 | @retval FALSE This buffer is not valid per processor architecture or overlaps\r | |
29 | with SMRAM.\r | |
30 | **/\r | |
31 | BOOLEAN\r | |
32 | VariableSmmIsBufferOutsideSmmValid (\r | |
33 | IN EFI_PHYSICAL_ADDRESS Buffer,\r | |
34 | IN UINT64 Length\r | |
35 | )\r | |
36 | {\r | |
37 | return TRUE;\r | |
38 | }\r | |
39 | \r | |
40 | /**\r | |
44289eea | 41 | Notify the system that the SMM variable driver is ready.\r |
688b2cad AB |
42 | **/\r |
43 | VOID\r | |
44 | VariableNotifySmmReady (\r | |
45 | VOID\r | |
46 | )\r | |
47 | {\r | |
48 | }\r | |
49 | \r | |
50 | /**\r | |
44289eea | 51 | Notify the system that the SMM variable write driver is ready.\r |
688b2cad AB |
52 | **/\r |
53 | VOID\r | |
54 | VariableNotifySmmWriteReady (\r | |
55 | VOID\r | |
56 | )\r | |
57 | {\r | |
58 | }\r | |
59 | \r | |
60 | /**\r | |
44289eea | 61 | Variable service MM driver entry point.\r |
688b2cad AB |
62 | \r |
63 | @param[in] ImageHandle A handle for the image that is initializing this\r | |
64 | driver\r | |
65 | @param[in] MmSystemTable A pointer to the MM system table\r | |
66 | \r | |
67 | @retval EFI_SUCCESS Variable service successfully initialized.\r | |
68 | **/\r | |
69 | EFI_STATUS\r | |
70 | EFIAPI\r | |
71 | VariableServiceInitialize (\r | |
72 | IN EFI_HANDLE ImageHandle,\r | |
73 | IN EFI_MM_SYSTEM_TABLE *MmSystemTable\r | |
74 | )\r | |
75 | {\r | |
76 | return MmVariableServiceInitialize ();\r | |
77 | }\r | |
78 | \r | |
79 | /**\r | |
80 | Whether the TCG or TCG2 protocols are installed in the UEFI protocol database.\r | |
81 | This information is used by the MorLock code to infer whether an existing\r | |
82 | MOR variable is legitimate or not.\r | |
83 | \r | |
84 | @retval TRUE Either the TCG or TCG2 protocol is installed in the UEFI\r | |
85 | protocol database\r | |
86 | @retval FALSE Neither the TCG nor the TCG2 protocol is installed in the UEFI\r | |
87 | protocol database\r | |
88 | **/\r | |
89 | BOOLEAN\r | |
90 | VariableHaveTcgProtocols (\r | |
91 | VOID\r | |
92 | )\r | |
93 | {\r | |
94 | return FALSE;\r | |
95 | }\r |