]> git.proxmox.com Git - mirror_edk2.git/blame - MdeModulePkg/Universal/FaultTolerantWriteDxe/FaultTolerantWriteSmm.c
1. Fix a bug when comparing two timestamp in auth-variable driver.
[mirror_edk2.git] / MdeModulePkg / Universal / FaultTolerantWriteDxe / FaultTolerantWriteSmm.c
CommitLineData
8a2d4996 1/** @file\r
2\r
3 This is a simple fault tolerant write driver that is intended to use in the SMM environment.\r
4\r
5 This boot service protocol only provides fault tolerant write capability for \r
6 block devices. The protocol has internal non-volatile intermediate storage \r
7 of the data and private information. It should be able to recover \r
8 automatically from a critical fault, such as power failure. \r
9\r
10 The implementation uses an FTW (Fault Tolerant Write) Work Space. \r
11 This work space is a memory copy of the work space on the Working Block,\r
12 the size of the work space is the FTW_WORK_SPACE_SIZE bytes.\r
13 \r
14 The work space stores each write record as EFI_FTW_RECORD structure.\r
15 The spare block stores the write buffer before write to the target block.\r
16 \r
17 The write record has three states to specify the different phase of write operation.\r
18 1) WRITE_ALLOCATED is that the record is allocated in write space.\r
19 The information of write operation is stored in write record structure.\r
20 2) SPARE_COMPLETED is that the data from write buffer is writed into the spare block as the backup.\r
21 3) WRITE_COMPLETED is that the data is copied from the spare block to the target block.\r
22\r
23 This driver operates the data as the whole size of spare block.\r
24 It first read the SpareAreaLength data from the target block into the spare memory buffer.\r
25 Then copy the write buffer data into the spare memory buffer.\r
26 Then write the spare memory buffer into the spare block.\r
27 Final copy the data from the spare block to the target block.\r
28\r
29 To make this drive work well, the following conditions must be satisfied:\r
30 1. The write NumBytes data must be fit within Spare area. \r
31 Offset + NumBytes <= SpareAreaLength\r
32 2. The whole flash range has the same block size.\r
33 3. Working block is an area which contains working space in its last block and has the same size as spare block.\r
34 4. Working Block area must be in the single one Firmware Volume Block range which FVB protocol is produced on. \r
35 5. Spare area must be in the single one Firmware Volume Block range which FVB protocol is produced on.\r
36 6. Any write data area (SpareAreaLength Area) which the data will be written into must be \r
37 in the single one Firmware Volume Block range which FVB protocol is produced on.\r
38 7. If write data area (such as Variable range) is enlarged, the spare area range must be enlarged.\r
39 The spare area must be enough large to store the write data before write them into the target range.\r
40 If one of them is not satisfied, FtwWrite may fail.\r
41 Usually, Spare area only takes one block. That's SpareAreaLength = BlockSize, NumberOfSpareBlock = 1.\r
42\r
c219324c
ED
43 Caution: This module requires additional review when modified.\r
44 This driver need to make sure the CommBuffer is not in the SMRAM range. \r
45\r
46Copyright (c) 2010 - 2012, Intel Corporation. All rights reserved.<BR>\r
8a2d4996 47This program and the accompanying materials \r
48are licensed and made available under the terms and conditions of the BSD License \r
49which accompanies this distribution. The full text of the license may be found at \r
50http://opensource.org/licenses/bsd-license.php \r
51 \r
52THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS, \r
53WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED. \r
54\r
55**/\r
56\r
f3b80a8e 57#include <PiSmm.h>\r
8a2d4996 58#include <Library/SmmServicesTableLib.h>\r
8a2d4996 59#include <Protocol/SmmSwapAddressRange.h>\r
f3b80a8e 60#include "FaultTolerantWrite.h"\r
61#include "FaultTolerantWriteSmmCommon.h"\r
c219324c 62#include <Protocol/SmmAccess2.h>\r
8a2d4996 63\r
64EFI_EVENT mFvbRegistration = NULL;\r
f3b80a8e 65EFI_FTW_DEVICE *mFtwDevice = NULL;\r
c219324c
ED
66EFI_SMRAM_DESCRIPTOR *mSmramRanges;\r
67UINTN mSmramRangeCount;\r
68\r
69\r
70/**\r
71 This function check if the address is in SMRAM.\r
72\r
73 @param Buffer the buffer address to be checked.\r
74 @param Length the buffer length to be checked.\r
75\r
76 @retval TRUE this address is in SMRAM.\r
77 @retval FALSE this address is NOT in SMRAM.\r
78**/\r
79BOOLEAN\r
80InternalIsAddressInSmram (\r
81 IN EFI_PHYSICAL_ADDRESS Buffer,\r
82 IN UINT64 Length\r
83 )\r
84{\r
85 UINTN Index;\r
86\r
87 for (Index = 0; Index < mSmramRangeCount; Index ++) {\r
88 if (((Buffer >= mSmramRanges[Index].CpuStart) && (Buffer < mSmramRanges[Index].CpuStart + mSmramRanges[Index].PhysicalSize)) ||\r
89 ((mSmramRanges[Index].CpuStart >= Buffer) && (mSmramRanges[Index].CpuStart < Buffer + Length))) {\r
90 return TRUE;\r
91 }\r
92 }\r
93\r
94 return FALSE;\r
95}\r
96\r
8a2d4996 97\r
98/**\r
99 Retrive the SMM FVB protocol interface by HANDLE.\r
100\r
101 @param[in] FvBlockHandle The handle of SMM FVB protocol that provides services for\r
102 reading, writing, and erasing the target block.\r
103 @param[out] FvBlock The interface of SMM FVB protocol\r
104\r
105 @retval EFI_SUCCESS The interface information for the specified protocol was returned.\r
106 @retval EFI_UNSUPPORTED The device does not support the SMM FVB protocol.\r
107 @retval EFI_INVALID_PARAMETER FvBlockHandle is not a valid EFI_HANDLE or FvBlock is NULL.\r
108\r
109**/\r
110EFI_STATUS\r
111FtwGetFvbByHandle (\r
112 IN EFI_HANDLE FvBlockHandle,\r
113 OUT EFI_FIRMWARE_VOLUME_BLOCK_PROTOCOL **FvBlock\r
114 )\r
115{\r
116 //\r
117 // To get the SMM FVB protocol interface on the handle\r
118 //\r
119 return gSmst->SmmHandleProtocol (\r
120 FvBlockHandle,\r
121 &gEfiSmmFirmwareVolumeBlockProtocolGuid,\r
122 (VOID **) FvBlock\r
123 );\r
124}\r
125\r
126/**\r
127 Retrive the SMM Swap Address Range protocol interface.\r
128\r
129 @param[out] SarProtocol The interface of SMM SAR protocol\r
130\r
131 @retval EFI_SUCCESS The SMM SAR protocol instance was found and returned in SarProtocol.\r
132 @retval EFI_NOT_FOUND The SMM SAR protocol instance was not found.\r
133 @retval EFI_INVALID_PARAMETER SarProtocol is NULL.\r
134\r
135**/\r
136EFI_STATUS\r
137FtwGetSarProtocol (\r
138 OUT VOID **SarProtocol\r
139 )\r
140{\r
141 EFI_STATUS Status;\r
142\r
143 //\r
144 // Locate Smm Swap Address Range protocol\r
145 //\r
146 Status = gSmst->SmmLocateProtocol (\r
147 &gEfiSmmSwapAddressRangeProtocolGuid, \r
148 NULL, \r
149 SarProtocol\r
150 );\r
151 return Status;\r
152}\r
153\r
154/**\r
155 Function returns an array of handles that support the SMM FVB protocol\r
156 in a buffer allocated from pool. \r
157\r
158 @param[out] NumberHandles The number of handles returned in Buffer.\r
159 @param[out] Buffer A pointer to the buffer to return the requested\r
160 array of handles that support SMM FVB protocol.\r
161\r
162 @retval EFI_SUCCESS The array of handles was returned in Buffer, and the number of\r
163 handles in Buffer was returned in NumberHandles.\r
164 @retval EFI_NOT_FOUND No SMM FVB handle was found.\r
165 @retval EFI_OUT_OF_RESOURCES There is not enough pool memory to store the matching results.\r
166 @retval EFI_INVALID_PARAMETER NumberHandles is NULL or Buffer is NULL.\r
167\r
168**/\r
169EFI_STATUS\r
170GetFvbCountAndBuffer (\r
171 OUT UINTN *NumberHandles,\r
172 OUT EFI_HANDLE **Buffer\r
173 )\r
174{\r
175 EFI_STATUS Status;\r
176 UINTN BufferSize;\r
177\r
178 if ((NumberHandles == NULL) || (Buffer == NULL)) {\r
179 return EFI_INVALID_PARAMETER;\r
180 }\r
181\r
182 BufferSize = 0;\r
183 *NumberHandles = 0;\r
184 *Buffer = NULL;\r
185 Status = gSmst->SmmLocateHandle (\r
186 ByProtocol,\r
187 &gEfiSmmFirmwareVolumeBlockProtocolGuid,\r
188 NULL,\r
189 &BufferSize,\r
190 *Buffer\r
191 );\r
192 if (EFI_ERROR(Status) && Status != EFI_BUFFER_TOO_SMALL) {\r
193 return EFI_NOT_FOUND;\r
194 }\r
195\r
196 *Buffer = AllocatePool (BufferSize);\r
197 if (*Buffer == NULL) {\r
198 return EFI_OUT_OF_RESOURCES;\r
199 }\r
200\r
201 Status = gSmst->SmmLocateHandle (\r
202 ByProtocol,\r
203 &gEfiSmmFirmwareVolumeBlockProtocolGuid,\r
204 NULL,\r
205 &BufferSize,\r
206 *Buffer\r
207 );\r
208\r
209 *NumberHandles = BufferSize / sizeof(EFI_HANDLE);\r
210 if (EFI_ERROR(Status)) {\r
211 *NumberHandles = 0;\r
212 }\r
213\r
214 return Status;\r
215}\r
216\r
217\r
f3b80a8e 218/**\r
219 Get the handle of the SMM FVB protocol by the FVB base address and attributes.\r
220\r
221 @param[in] Address The base address of SMM FVB protocol.\r
222 @param[in] Attributes The attributes of the SMM FVB protocol.\r
223 @param[out] SmmFvbHandle The handle of the SMM FVB protocol.\r
224\r
225 @retval EFI_SUCCESS The FVB handle is found.\r
226 @retval EFI_ABORTED The FVB protocol is not found.\r
227\r
228**/\r
229EFI_STATUS\r
230GetFvbByAddressAndAttribute (\r
231 IN EFI_PHYSICAL_ADDRESS Address,\r
232 IN EFI_FVB_ATTRIBUTES_2 Attributes,\r
233 OUT EFI_HANDLE *SmmFvbHandle\r
234 )\r
235{\r
236 EFI_STATUS Status;\r
237 EFI_HANDLE *HandleBuffer;\r
238 UINTN HandleCount;\r
239 UINTN Index;\r
240 EFI_PHYSICAL_ADDRESS FvbBaseAddress;\r
241 EFI_FVB_ATTRIBUTES_2 FvbAttributes;\r
242 EFI_FIRMWARE_VOLUME_BLOCK_PROTOCOL *Fvb;\r
243\r
244 //\r
245 // Locate all handles of SMM Fvb protocol.\r
246 //\r
247 Status = GetFvbCountAndBuffer (&HandleCount, &HandleBuffer);\r
248 if (EFI_ERROR (Status)) {\r
249 return EFI_ABORTED;\r
250 }\r
251 \r
252 //\r
253 // Find the proper SMM Fvb handle by the address and attributes.\r
254 //\r
255 for (Index = 0; Index < HandleCount; Index++) {\r
256 Status = FtwGetFvbByHandle (HandleBuffer[Index], &Fvb);\r
257 if (EFI_ERROR (Status)) {\r
258 break;\r
259 }\r
260 //\r
261 // Compare the address.\r
262 //\r
263 Status = Fvb->GetPhysicalAddress (Fvb, &FvbBaseAddress);\r
264 if (EFI_ERROR (Status)) {\r
265 continue;\r
266 }\r
267 if (Address != FvbBaseAddress) {\r
268 continue;\r
269 }\r
270\r
271 //\r
272 // Compare the attribute.\r
273 //\r
274 Status = Fvb->GetAttributes (Fvb, &FvbAttributes);\r
275 if (EFI_ERROR (Status)) {\r
276 continue;\r
277 }\r
278 if (Attributes != FvbAttributes) {\r
279 continue;\r
280 }\r
281\r
282 //\r
283 // Found the proper FVB handle.\r
284 //\r
285 *SmmFvbHandle = HandleBuffer[Index];\r
286 FreePool (HandleBuffer);\r
287 return EFI_SUCCESS;\r
288 }\r
289\r
290 FreePool (HandleBuffer);\r
291 return EFI_ABORTED;\r
292}\r
293\r
294/**\r
295 Communication service SMI Handler entry.\r
296\r
297 This SMI handler provides services for the fault tolerant write wrapper driver.\r
298\r
c219324c
ED
299 Caution: This function requires additional review when modified.\r
300 This driver need to make sure the CommBuffer is not in the SMRAM range. \r
301 Also in FTW_FUNCTION_GET_LAST_WRITE case, check SmmFtwGetLastWriteHeader->Data + \r
302 SmmFtwGetLastWriteHeader->PrivateDataSize within communication buffer.\r
303\r
f3b80a8e 304 @param[in] DispatchHandle The unique handle assigned to this handler by SmiHandlerRegister().\r
305 @param[in] RegisterContext Points to an optional handler context which was specified when the\r
306 handler was registered.\r
307 @param[in, out] CommBuffer A pointer to a collection of data in memory that will be conveyed\r
308 from a non-SMM environment into an SMM environment.\r
309 @param[in, out] CommBufferSize The size of the CommBuffer.\r
310\r
311 @retval EFI_SUCCESS The interrupt was handled and quiesced. No other handlers \r
312 should still be called.\r
313 @retval EFI_WARN_INTERRUPT_SOURCE_QUIESCED The interrupt has been quiesced but other handlers should \r
314 still be called.\r
315 @retval EFI_WARN_INTERRUPT_SOURCE_PENDING The interrupt is still pending and other handlers should still \r
316 be called.\r
317 @retval EFI_INTERRUPT_PENDING The interrupt could not be quiesced.\r
318 \r
319**/\r
320EFI_STATUS\r
321EFIAPI\r
322SmmFaultTolerantWriteHandler (\r
323 IN EFI_HANDLE DispatchHandle,\r
324 IN CONST VOID *RegisterContext,\r
325 IN OUT VOID *CommBuffer,\r
326 IN OUT UINTN *CommBufferSize\r
327 )\r
328{\r
329 EFI_STATUS Status;\r
330 SMM_FTW_COMMUNICATE_FUNCTION_HEADER *SmmFtwFunctionHeader;\r
331 SMM_FTW_GET_MAX_BLOCK_SIZE_HEADER *SmmGetMaxBlockSizeHeader;\r
332 SMM_FTW_ALLOCATE_HEADER *SmmFtwAllocateHeader;\r
333 SMM_FTW_WRITE_HEADER *SmmFtwWriteHeader;\r
334 SMM_FTW_RESTART_HEADER *SmmFtwRestartHeader;\r
335 SMM_FTW_GET_LAST_WRITE_HEADER *SmmFtwGetLastWriteHeader;\r
336 VOID *PrivateData;\r
337 EFI_HANDLE SmmFvbHandle;\r
338\r
339 ASSERT (CommBuffer != NULL);\r
340 ASSERT (CommBufferSize != NULL);\r
341\r
c219324c
ED
342 if (InternalIsAddressInSmram ((EFI_PHYSICAL_ADDRESS)(UINTN)CommBuffer, *CommBufferSize)) {\r
343 DEBUG ((EFI_D_ERROR, "SMM communication buffer size is in SMRAM!\n"));\r
344 return EFI_SUCCESS;\r
345 }\r
346\r
f3b80a8e 347 SmmFtwFunctionHeader = (SMM_FTW_COMMUNICATE_FUNCTION_HEADER *)CommBuffer;\r
348 switch (SmmFtwFunctionHeader->Function) {\r
349 case FTW_FUNCTION_GET_MAX_BLOCK_SIZE:\r
350 SmmGetMaxBlockSizeHeader = (SMM_FTW_GET_MAX_BLOCK_SIZE_HEADER *) SmmFtwFunctionHeader->Data; \r
351 Status = FtwGetMaxBlockSize (\r
352 &mFtwDevice->FtwInstance,\r
353 &SmmGetMaxBlockSizeHeader->BlockSize\r
354 );\r
355 break;\r
356 \r
357 case FTW_FUNCTION_ALLOCATE:\r
358 SmmFtwAllocateHeader = (SMM_FTW_ALLOCATE_HEADER *) SmmFtwFunctionHeader->Data;\r
359 Status = FtwAllocate (\r
360 &mFtwDevice->FtwInstance,\r
361 &SmmFtwAllocateHeader->CallerId,\r
362 SmmFtwAllocateHeader->PrivateDataSize,\r
363 SmmFtwAllocateHeader->NumberOfWrites\r
364 );\r
365 break;\r
366 \r
367 case FTW_FUNCTION_WRITE:\r
368 SmmFtwWriteHeader = (SMM_FTW_WRITE_HEADER *) SmmFtwFunctionHeader->Data;\r
369 if (SmmFtwWriteHeader->PrivateDataSize == 0) {\r
370 PrivateData = NULL;\r
371 } else {\r
372 PrivateData = (VOID *)&SmmFtwWriteHeader->Data[SmmFtwWriteHeader->Length];\r
373 }\r
374 Status = GetFvbByAddressAndAttribute (\r
375 SmmFtwWriteHeader->FvbBaseAddress, \r
376 SmmFtwWriteHeader->FvbAttributes,\r
377 &SmmFvbHandle\r
378 );\r
379 if (!EFI_ERROR (Status)) {\r
380 Status = FtwWrite(\r
381 &mFtwDevice->FtwInstance,\r
382 SmmFtwWriteHeader->Lba,\r
383 SmmFtwWriteHeader->Offset,\r
384 SmmFtwWriteHeader->Length,\r
385 PrivateData,\r
386 SmmFvbHandle,\r
387 SmmFtwWriteHeader->Data\r
388 );\r
389 }\r
390 break;\r
391 \r
392 case FTW_FUNCTION_RESTART:\r
393 SmmFtwRestartHeader = (SMM_FTW_RESTART_HEADER *) SmmFtwFunctionHeader->Data;\r
394 Status = GetFvbByAddressAndAttribute (\r
395 SmmFtwRestartHeader->FvbBaseAddress, \r
396 SmmFtwRestartHeader->FvbAttributes,\r
397 &SmmFvbHandle\r
398 ); \r
399 if (!EFI_ERROR (Status)) {\r
400 Status = FtwRestart (&mFtwDevice->FtwInstance, SmmFvbHandle);\r
401 }\r
402 break;\r
403\r
404 case FTW_FUNCTION_ABORT:\r
405 Status = FtwAbort (&mFtwDevice->FtwInstance);\r
406 break;\r
407 \r
408 case FTW_FUNCTION_GET_LAST_WRITE:\r
409 SmmFtwGetLastWriteHeader = (SMM_FTW_GET_LAST_WRITE_HEADER *) SmmFtwFunctionHeader->Data;\r
c219324c
ED
410 if (((UINT8*)SmmFtwGetLastWriteHeader->Data > (UINT8*)CommBuffer) && \r
411 ((UINT8*)SmmFtwGetLastWriteHeader->Data + SmmFtwGetLastWriteHeader->PrivateDataSize <= (UINT8*)CommBuffer + (*CommBufferSize))) {\r
412 Status = FtwGetLastWrite (\r
413 &mFtwDevice->FtwInstance,\r
414 &SmmFtwGetLastWriteHeader->CallerId,\r
415 &SmmFtwGetLastWriteHeader->Lba,\r
416 &SmmFtwGetLastWriteHeader->Offset,\r
417 &SmmFtwGetLastWriteHeader->Length,\r
418 &SmmFtwGetLastWriteHeader->PrivateDataSize,\r
419 (VOID *)SmmFtwGetLastWriteHeader->Data,\r
420 &SmmFtwGetLastWriteHeader->Complete\r
421 );\r
422 } else {\r
423 Status = EFI_INVALID_PARAMETER;\r
424 }\r
f3b80a8e 425 break;\r
426\r
427 default:\r
f3b80a8e 428 Status = EFI_UNSUPPORTED;\r
429 }\r
430\r
431 SmmFtwFunctionHeader->ReturnStatus = Status;\r
432\r
433 return EFI_SUCCESS;\r
434}\r
435\r
436\r
8a2d4996 437/**\r
438 SMM Firmware Volume Block Protocol notification event handler.\r
439 \r
440 @param[in] Protocol Points to the protocol's unique identifier\r
441 @param[in] Interface Points to the interface instance\r
442 @param[in] Handle The handle on which the interface was installed\r
443\r
444 @retval EFI_SUCCESS SmmEventCallback runs successfully\r
445 \r
446 **/\r
447EFI_STATUS\r
448EFIAPI\r
449FvbNotificationEvent (\r
450 IN CONST EFI_GUID *Protocol,\r
451 IN VOID *Interface,\r
452 IN EFI_HANDLE Handle\r
453 )\r
454{\r
455 EFI_STATUS Status;\r
456 EFI_SMM_FAULT_TOLERANT_WRITE_PROTOCOL *FtwProtocol;\r
f3b80a8e 457 EFI_HANDLE SmmFtwHandle;\r
8a2d4996 458 \r
459 //\r
460 // Just return to avoid install SMM FaultTolerantWriteProtocol again\r
461 // if SMM Fault Tolerant Write protocol had been installed.\r
462 // \r
463 Status = gSmst->SmmLocateProtocol (\r
464 &gEfiSmmFaultTolerantWriteProtocolGuid, \r
465 NULL, \r
466 (VOID **) &FtwProtocol\r
467 );\r
468 if (!EFI_ERROR (Status)) {\r
469 return EFI_SUCCESS;\r
470 }\r
471\r
472 //\r
473 // Found proper FVB protocol and initialize FtwDevice for protocol installation\r
474 //\r
f3b80a8e 475 Status = InitFtwProtocol (mFtwDevice);\r
8a2d4996 476 if (EFI_ERROR(Status)) {\r
477 return Status;\r
478 }\r
479 \r
480 //\r
481 // Install protocol interface\r
482 //\r
483 Status = gSmst->SmmInstallProtocolInterface (\r
f3b80a8e 484 &mFtwDevice->Handle,\r
8a2d4996 485 &gEfiSmmFaultTolerantWriteProtocolGuid,\r
486 EFI_NATIVE_INTERFACE,\r
f3b80a8e 487 &mFtwDevice->FtwInstance\r
8a2d4996 488 );\r
489 ASSERT_EFI_ERROR (Status); \r
f3b80a8e 490\r
491 //\r
492 // Notify the Ftw wrapper driver SMM Ftw is ready\r
493 //\r
494 SmmFtwHandle = NULL;\r
495 Status = gBS->InstallProtocolInterface (\r
496 &SmmFtwHandle,\r
497 &gEfiSmmFaultTolerantWriteProtocolGuid,\r
498 EFI_NATIVE_INTERFACE,\r
499 NULL\r
500 );\r
501 ASSERT_EFI_ERROR (Status);\r
8a2d4996 502 \r
503 return EFI_SUCCESS;\r
504}\r
505\r
506\r
507/**\r
508 This function is the entry point of the Fault Tolerant Write driver.\r
509\r
510 @param[in] ImageHandle A handle for the image that is initializing this driver\r
511 @param[in] SystemTable A pointer to the EFI system table\r
512\r
513 @retval EFI_SUCCESS The initialization finished successfully.\r
514 @retval EFI_OUT_OF_RESOURCES Allocate memory error\r
515 @retval EFI_INVALID_PARAMETER Workspace or Spare block does not exist\r
516\r
517**/\r
518EFI_STATUS\r
519EFIAPI\r
520SmmFaultTolerantWriteInitialize (\r
521 IN EFI_HANDLE ImageHandle,\r
522 IN EFI_SYSTEM_TABLE *SystemTable\r
523 )\r
524{\r
525 EFI_STATUS Status;\r
f3b80a8e 526 EFI_HANDLE FtwHandle;\r
c219324c
ED
527 EFI_SMM_ACCESS2_PROTOCOL *SmmAccess;\r
528 UINTN Size;\r
f3b80a8e 529 \r
8a2d4996 530 //\r
531 // Allocate private data structure for SMM FTW protocol and do some initialization\r
532 //\r
f3b80a8e 533 Status = InitFtwDevice (&mFtwDevice);\r
8a2d4996 534 if (EFI_ERROR(Status)) {\r
535 return Status;\r
536 }\r
c219324c
ED
537\r
538 //\r
539 // Get SMRAM information\r
540 //\r
541 Status = gBS->LocateProtocol (&gEfiSmmAccess2ProtocolGuid, NULL, (VOID **)&SmmAccess);\r
542 ASSERT_EFI_ERROR (Status);\r
543\r
544 Size = 0;\r
545 Status = SmmAccess->GetCapabilities (SmmAccess, &Size, NULL);\r
546 ASSERT (Status == EFI_BUFFER_TOO_SMALL);\r
547\r
548 Status = gSmst->SmmAllocatePool (\r
549 EfiRuntimeServicesData,\r
550 Size,\r
551 (VOID **)&mSmramRanges\r
552 );\r
553 ASSERT_EFI_ERROR (Status);\r
554\r
555 Status = SmmAccess->GetCapabilities (SmmAccess, &Size, mSmramRanges);\r
556 ASSERT_EFI_ERROR (Status);\r
557\r
558 mSmramRangeCount = Size / sizeof (EFI_SMRAM_DESCRIPTOR);\r
559\r
8a2d4996 560 //\r
561 // Register FvbNotificationEvent () notify function.\r
562 // \r
563 Status = gSmst->SmmRegisterProtocolNotify (\r
564 &gEfiSmmFirmwareVolumeBlockProtocolGuid,\r
565 FvbNotificationEvent,\r
566 &mFvbRegistration\r
567 );\r
568 ASSERT_EFI_ERROR (Status);\r
569\r
570 FvbNotificationEvent (NULL, NULL, NULL);\r
f3b80a8e 571\r
572 ///\r
573 /// Register SMM FTW SMI handler\r
574 ///\r
575 Status = gSmst->SmiHandlerRegister (SmmFaultTolerantWriteHandler, &gEfiSmmFaultTolerantWriteProtocolGuid, &FtwHandle);\r
576 ASSERT_EFI_ERROR (Status);\r
8a2d4996 577 \r
578 return EFI_SUCCESS;\r
579}\r