]> git.proxmox.com Git - mirror_edk2.git/blame - MdeModulePkg/Universal/FaultTolerantWriteDxe/FaultTolerantWriteSmm.c
Read/Write memory space including MMIO range with the width requested from HOST.
[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
f07268bd 46Copyright (c) 2010 - 2013, 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
f07268bd 63#include <Protocol/SmmEndOfDxe.h>\r
8a2d4996 64\r
65EFI_EVENT mFvbRegistration = NULL;\r
f3b80a8e 66EFI_FTW_DEVICE *mFtwDevice = NULL;\r
c219324c
ED
67EFI_SMRAM_DESCRIPTOR *mSmramRanges;\r
68UINTN mSmramRangeCount;\r
69\r
f07268bd
SZ
70///\r
71/// The flag to indicate whether the platform has left the DXE phase of execution.\r
72///\r
73BOOLEAN mEndOfDxe = FALSE;\r
c219324c
ED
74\r
75/**\r
76 This function check if the address is in SMRAM.\r
77\r
78 @param Buffer the buffer address to be checked.\r
79 @param Length the buffer length to be checked.\r
80\r
81 @retval TRUE this address is in SMRAM.\r
82 @retval FALSE this address is NOT in SMRAM.\r
83**/\r
84BOOLEAN\r
85InternalIsAddressInSmram (\r
86 IN EFI_PHYSICAL_ADDRESS Buffer,\r
87 IN UINT64 Length\r
88 )\r
89{\r
90 UINTN Index;\r
91\r
92 for (Index = 0; Index < mSmramRangeCount; Index ++) {\r
93 if (((Buffer >= mSmramRanges[Index].CpuStart) && (Buffer < mSmramRanges[Index].CpuStart + mSmramRanges[Index].PhysicalSize)) ||\r
94 ((mSmramRanges[Index].CpuStart >= Buffer) && (mSmramRanges[Index].CpuStart < Buffer + Length))) {\r
95 return TRUE;\r
96 }\r
97 }\r
98\r
99 return FALSE;\r
100}\r
101\r
9d00d20e
SZ
102/**\r
103 This function check if the address refered by Buffer and Length is valid.\r
104\r
105 @param Buffer the buffer address to be checked.\r
106 @param Length the buffer length to be checked.\r
107\r
108 @retval TRUE this address is valid.\r
109 @retval FALSE this address is NOT valid.\r
110**/\r
111BOOLEAN\r
112InternalIsAddressValid (\r
113 IN UINTN Buffer,\r
114 IN UINTN Length\r
115 )\r
116{\r
117 if (Buffer > (MAX_ADDRESS - Length)) {\r
118 //\r
119 // Overflow happen\r
120 //\r
121 return FALSE;\r
122 }\r
123 if (InternalIsAddressInSmram ((EFI_PHYSICAL_ADDRESS)Buffer, (UINT64)Length)) {\r
124 return FALSE;\r
125 }\r
126 return TRUE;\r
127}\r
8a2d4996 128\r
129/**\r
130 Retrive the SMM FVB protocol interface by HANDLE.\r
131\r
132 @param[in] FvBlockHandle The handle of SMM FVB protocol that provides services for\r
133 reading, writing, and erasing the target block.\r
134 @param[out] FvBlock The interface of SMM FVB protocol\r
135\r
136 @retval EFI_SUCCESS The interface information for the specified protocol was returned.\r
137 @retval EFI_UNSUPPORTED The device does not support the SMM FVB protocol.\r
138 @retval EFI_INVALID_PARAMETER FvBlockHandle is not a valid EFI_HANDLE or FvBlock is NULL.\r
139\r
140**/\r
141EFI_STATUS\r
142FtwGetFvbByHandle (\r
143 IN EFI_HANDLE FvBlockHandle,\r
144 OUT EFI_FIRMWARE_VOLUME_BLOCK_PROTOCOL **FvBlock\r
145 )\r
146{\r
147 //\r
148 // To get the SMM FVB protocol interface on the handle\r
149 //\r
150 return gSmst->SmmHandleProtocol (\r
151 FvBlockHandle,\r
152 &gEfiSmmFirmwareVolumeBlockProtocolGuid,\r
153 (VOID **) FvBlock\r
154 );\r
155}\r
156\r
157/**\r
158 Retrive the SMM Swap Address Range protocol interface.\r
159\r
160 @param[out] SarProtocol The interface of SMM SAR protocol\r
161\r
162 @retval EFI_SUCCESS The SMM SAR protocol instance was found and returned in SarProtocol.\r
163 @retval EFI_NOT_FOUND The SMM SAR protocol instance was not found.\r
164 @retval EFI_INVALID_PARAMETER SarProtocol is NULL.\r
165\r
166**/\r
167EFI_STATUS\r
168FtwGetSarProtocol (\r
169 OUT VOID **SarProtocol\r
170 )\r
171{\r
172 EFI_STATUS Status;\r
173\r
174 //\r
175 // Locate Smm Swap Address Range protocol\r
176 //\r
177 Status = gSmst->SmmLocateProtocol (\r
178 &gEfiSmmSwapAddressRangeProtocolGuid, \r
179 NULL, \r
180 SarProtocol\r
181 );\r
182 return Status;\r
183}\r
184\r
185/**\r
186 Function returns an array of handles that support the SMM FVB protocol\r
187 in a buffer allocated from pool. \r
188\r
189 @param[out] NumberHandles The number of handles returned in Buffer.\r
190 @param[out] Buffer A pointer to the buffer to return the requested\r
191 array of handles that support SMM FVB protocol.\r
192\r
193 @retval EFI_SUCCESS The array of handles was returned in Buffer, and the number of\r
194 handles in Buffer was returned in NumberHandles.\r
195 @retval EFI_NOT_FOUND No SMM FVB handle was found.\r
196 @retval EFI_OUT_OF_RESOURCES There is not enough pool memory to store the matching results.\r
197 @retval EFI_INVALID_PARAMETER NumberHandles is NULL or Buffer is NULL.\r
198\r
199**/\r
200EFI_STATUS\r
201GetFvbCountAndBuffer (\r
202 OUT UINTN *NumberHandles,\r
203 OUT EFI_HANDLE **Buffer\r
204 )\r
205{\r
206 EFI_STATUS Status;\r
207 UINTN BufferSize;\r
208\r
209 if ((NumberHandles == NULL) || (Buffer == NULL)) {\r
210 return EFI_INVALID_PARAMETER;\r
211 }\r
212\r
213 BufferSize = 0;\r
214 *NumberHandles = 0;\r
215 *Buffer = NULL;\r
216 Status = gSmst->SmmLocateHandle (\r
217 ByProtocol,\r
218 &gEfiSmmFirmwareVolumeBlockProtocolGuid,\r
219 NULL,\r
220 &BufferSize,\r
221 *Buffer\r
222 );\r
223 if (EFI_ERROR(Status) && Status != EFI_BUFFER_TOO_SMALL) {\r
224 return EFI_NOT_FOUND;\r
225 }\r
226\r
227 *Buffer = AllocatePool (BufferSize);\r
228 if (*Buffer == NULL) {\r
229 return EFI_OUT_OF_RESOURCES;\r
230 }\r
231\r
232 Status = gSmst->SmmLocateHandle (\r
233 ByProtocol,\r
234 &gEfiSmmFirmwareVolumeBlockProtocolGuid,\r
235 NULL,\r
236 &BufferSize,\r
237 *Buffer\r
238 );\r
239\r
240 *NumberHandles = BufferSize / sizeof(EFI_HANDLE);\r
241 if (EFI_ERROR(Status)) {\r
242 *NumberHandles = 0;\r
d26c7e82
SZ
243 FreePool (*Buffer);\r
244 *Buffer = NULL;\r
8a2d4996 245 }\r
246\r
247 return Status;\r
248}\r
249\r
250\r
f3b80a8e 251/**\r
252 Get the handle of the SMM FVB protocol by the FVB base address and attributes.\r
253\r
254 @param[in] Address The base address of SMM FVB protocol.\r
255 @param[in] Attributes The attributes of the SMM FVB protocol.\r
256 @param[out] SmmFvbHandle The handle of the SMM FVB protocol.\r
257\r
258 @retval EFI_SUCCESS The FVB handle is found.\r
259 @retval EFI_ABORTED The FVB protocol is not found.\r
260\r
261**/\r
262EFI_STATUS\r
263GetFvbByAddressAndAttribute (\r
264 IN EFI_PHYSICAL_ADDRESS Address,\r
265 IN EFI_FVB_ATTRIBUTES_2 Attributes,\r
266 OUT EFI_HANDLE *SmmFvbHandle\r
267 )\r
268{\r
269 EFI_STATUS Status;\r
270 EFI_HANDLE *HandleBuffer;\r
271 UINTN HandleCount;\r
272 UINTN Index;\r
273 EFI_PHYSICAL_ADDRESS FvbBaseAddress;\r
274 EFI_FVB_ATTRIBUTES_2 FvbAttributes;\r
275 EFI_FIRMWARE_VOLUME_BLOCK_PROTOCOL *Fvb;\r
276\r
277 //\r
278 // Locate all handles of SMM Fvb protocol.\r
279 //\r
280 Status = GetFvbCountAndBuffer (&HandleCount, &HandleBuffer);\r
281 if (EFI_ERROR (Status)) {\r
282 return EFI_ABORTED;\r
283 }\r
284 \r
285 //\r
286 // Find the proper SMM Fvb handle by the address and attributes.\r
287 //\r
288 for (Index = 0; Index < HandleCount; Index++) {\r
289 Status = FtwGetFvbByHandle (HandleBuffer[Index], &Fvb);\r
290 if (EFI_ERROR (Status)) {\r
291 break;\r
292 }\r
293 //\r
294 // Compare the address.\r
295 //\r
296 Status = Fvb->GetPhysicalAddress (Fvb, &FvbBaseAddress);\r
297 if (EFI_ERROR (Status)) {\r
298 continue;\r
299 }\r
300 if (Address != FvbBaseAddress) {\r
301 continue;\r
302 }\r
303\r
304 //\r
305 // Compare the attribute.\r
306 //\r
307 Status = Fvb->GetAttributes (Fvb, &FvbAttributes);\r
308 if (EFI_ERROR (Status)) {\r
309 continue;\r
310 }\r
311 if (Attributes != FvbAttributes) {\r
312 continue;\r
313 }\r
314\r
315 //\r
316 // Found the proper FVB handle.\r
317 //\r
318 *SmmFvbHandle = HandleBuffer[Index];\r
319 FreePool (HandleBuffer);\r
320 return EFI_SUCCESS;\r
321 }\r
322\r
323 FreePool (HandleBuffer);\r
324 return EFI_ABORTED;\r
325}\r
326\r
327/**\r
328 Communication service SMI Handler entry.\r
329\r
330 This SMI handler provides services for the fault tolerant write wrapper driver.\r
331\r
c219324c
ED
332 Caution: This function requires additional review when modified.\r
333 This driver need to make sure the CommBuffer is not in the SMRAM range. \r
334 Also in FTW_FUNCTION_GET_LAST_WRITE case, check SmmFtwGetLastWriteHeader->Data + \r
335 SmmFtwGetLastWriteHeader->PrivateDataSize within communication buffer.\r
336\r
f3b80a8e 337 @param[in] DispatchHandle The unique handle assigned to this handler by SmiHandlerRegister().\r
338 @param[in] RegisterContext Points to an optional handler context which was specified when the\r
339 handler was registered.\r
340 @param[in, out] CommBuffer A pointer to a collection of data in memory that will be conveyed\r
341 from a non-SMM environment into an SMM environment.\r
342 @param[in, out] CommBufferSize The size of the CommBuffer.\r
343\r
344 @retval EFI_SUCCESS The interrupt was handled and quiesced. No other handlers \r
345 should still be called.\r
346 @retval EFI_WARN_INTERRUPT_SOURCE_QUIESCED The interrupt has been quiesced but other handlers should \r
347 still be called.\r
348 @retval EFI_WARN_INTERRUPT_SOURCE_PENDING The interrupt is still pending and other handlers should still \r
349 be called.\r
350 @retval EFI_INTERRUPT_PENDING The interrupt could not be quiesced.\r
351 \r
352**/\r
353EFI_STATUS\r
354EFIAPI\r
355SmmFaultTolerantWriteHandler (\r
356 IN EFI_HANDLE DispatchHandle,\r
357 IN CONST VOID *RegisterContext,\r
358 IN OUT VOID *CommBuffer,\r
359 IN OUT UINTN *CommBufferSize\r
360 )\r
361{\r
362 EFI_STATUS Status;\r
363 SMM_FTW_COMMUNICATE_FUNCTION_HEADER *SmmFtwFunctionHeader;\r
364 SMM_FTW_GET_MAX_BLOCK_SIZE_HEADER *SmmGetMaxBlockSizeHeader;\r
365 SMM_FTW_ALLOCATE_HEADER *SmmFtwAllocateHeader;\r
366 SMM_FTW_WRITE_HEADER *SmmFtwWriteHeader;\r
367 SMM_FTW_RESTART_HEADER *SmmFtwRestartHeader;\r
368 SMM_FTW_GET_LAST_WRITE_HEADER *SmmFtwGetLastWriteHeader;\r
369 VOID *PrivateData;\r
370 EFI_HANDLE SmmFvbHandle;\r
7ea4cf3f 371 UINTN InfoSize;\r
f3b80a8e 372\r
7ea4cf3f
SZ
373\r
374 //\r
375 // If input is invalid, stop processing this SMI\r
376 //\r
377 if (CommBuffer == NULL || CommBufferSize == NULL) {\r
378 return EFI_SUCCESS;\r
379 }\r
380\r
381 if (*CommBufferSize < SMM_FTW_COMMUNICATE_HEADER_SIZE) {\r
382 return EFI_SUCCESS;\r
383 }\r
f3b80a8e 384\r
9d00d20e
SZ
385 if (!InternalIsAddressValid ((UINTN)CommBuffer, *CommBufferSize)) {\r
386 DEBUG ((EFI_D_ERROR, "SMM communication buffer in SMRAM or overflow!\n"));\r
c219324c
ED
387 return EFI_SUCCESS;\r
388 }\r
389\r
f3b80a8e 390 SmmFtwFunctionHeader = (SMM_FTW_COMMUNICATE_FUNCTION_HEADER *)CommBuffer;\r
f07268bd
SZ
391\r
392 if (mEndOfDxe) {\r
393 //\r
394 // It will be not safe to expose the operations after End Of Dxe.\r
395 //\r
396 DEBUG ((EFI_D_ERROR, "SmmFtwHandler: Not safe to do the operation: %x after End Of Dxe, so access denied!\n", SmmFtwFunctionHeader->Function));\r
397 SmmFtwFunctionHeader->ReturnStatus = EFI_ACCESS_DENIED;\r
398 return EFI_SUCCESS;\r
399 }\r
400\r
f3b80a8e 401 switch (SmmFtwFunctionHeader->Function) {\r
402 case FTW_FUNCTION_GET_MAX_BLOCK_SIZE:\r
7ea4cf3f
SZ
403 SmmGetMaxBlockSizeHeader = (SMM_FTW_GET_MAX_BLOCK_SIZE_HEADER *) SmmFtwFunctionHeader->Data;\r
404 InfoSize = sizeof (SMM_FTW_GET_MAX_BLOCK_SIZE_HEADER);\r
405\r
406 //\r
407 // SMRAM range check already covered before\r
408 //\r
409 if (InfoSize > *CommBufferSize - SMM_FTW_COMMUNICATE_HEADER_SIZE) {\r
410 DEBUG ((EFI_D_ERROR, "Data size exceed communication buffer size limit!\n"));\r
411 Status = EFI_ACCESS_DENIED;\r
412 break;\r
413 }\r
414\r
f3b80a8e 415 Status = FtwGetMaxBlockSize (\r
416 &mFtwDevice->FtwInstance,\r
417 &SmmGetMaxBlockSizeHeader->BlockSize\r
418 );\r
419 break;\r
420 \r
421 case FTW_FUNCTION_ALLOCATE:\r
422 SmmFtwAllocateHeader = (SMM_FTW_ALLOCATE_HEADER *) SmmFtwFunctionHeader->Data;\r
423 Status = FtwAllocate (\r
424 &mFtwDevice->FtwInstance,\r
425 &SmmFtwAllocateHeader->CallerId,\r
426 SmmFtwAllocateHeader->PrivateDataSize,\r
427 SmmFtwAllocateHeader->NumberOfWrites\r
428 );\r
429 break;\r
430 \r
431 case FTW_FUNCTION_WRITE:\r
432 SmmFtwWriteHeader = (SMM_FTW_WRITE_HEADER *) SmmFtwFunctionHeader->Data;\r
433 if (SmmFtwWriteHeader->PrivateDataSize == 0) {\r
434 PrivateData = NULL;\r
435 } else {\r
436 PrivateData = (VOID *)&SmmFtwWriteHeader->Data[SmmFtwWriteHeader->Length];\r
437 }\r
438 Status = GetFvbByAddressAndAttribute (\r
439 SmmFtwWriteHeader->FvbBaseAddress, \r
440 SmmFtwWriteHeader->FvbAttributes,\r
441 &SmmFvbHandle\r
442 );\r
443 if (!EFI_ERROR (Status)) {\r
444 Status = FtwWrite(\r
445 &mFtwDevice->FtwInstance,\r
446 SmmFtwWriteHeader->Lba,\r
447 SmmFtwWriteHeader->Offset,\r
448 SmmFtwWriteHeader->Length,\r
449 PrivateData,\r
450 SmmFvbHandle,\r
451 SmmFtwWriteHeader->Data\r
452 );\r
453 }\r
454 break;\r
455 \r
456 case FTW_FUNCTION_RESTART:\r
457 SmmFtwRestartHeader = (SMM_FTW_RESTART_HEADER *) SmmFtwFunctionHeader->Data;\r
458 Status = GetFvbByAddressAndAttribute (\r
459 SmmFtwRestartHeader->FvbBaseAddress, \r
460 SmmFtwRestartHeader->FvbAttributes,\r
461 &SmmFvbHandle\r
462 ); \r
463 if (!EFI_ERROR (Status)) {\r
464 Status = FtwRestart (&mFtwDevice->FtwInstance, SmmFvbHandle);\r
465 }\r
466 break;\r
467\r
468 case FTW_FUNCTION_ABORT:\r
469 Status = FtwAbort (&mFtwDevice->FtwInstance);\r
470 break;\r
471 \r
472 case FTW_FUNCTION_GET_LAST_WRITE:\r
473 SmmFtwGetLastWriteHeader = (SMM_FTW_GET_LAST_WRITE_HEADER *) SmmFtwFunctionHeader->Data;\r
f07268bd
SZ
474 if ((UINTN)(~0) - SmmFtwGetLastWriteHeader->PrivateDataSize < OFFSET_OF (SMM_FTW_GET_LAST_WRITE_HEADER, Data)){\r
475 //\r
476 // Prevent InfoSize overflow\r
477 //\r
478 Status = EFI_ACCESS_DENIED;\r
479 break;\r
480 }\r
7ea4cf3f
SZ
481 InfoSize = OFFSET_OF (SMM_FTW_GET_LAST_WRITE_HEADER, Data) + SmmFtwGetLastWriteHeader->PrivateDataSize;\r
482\r
483 //\r
484 // SMRAM range check already covered before\r
485 //\r
486 if (InfoSize > *CommBufferSize - SMM_FTW_COMMUNICATE_HEADER_SIZE) {\r
487 DEBUG ((EFI_D_ERROR, "Data size exceed communication buffer size limit!\n"));\r
488 Status = EFI_ACCESS_DENIED;\r
489 break;\r
c219324c 490 }\r
7ea4cf3f
SZ
491\r
492 Status = FtwGetLastWrite (\r
493 &mFtwDevice->FtwInstance,\r
494 &SmmFtwGetLastWriteHeader->CallerId,\r
495 &SmmFtwGetLastWriteHeader->Lba,\r
496 &SmmFtwGetLastWriteHeader->Offset,\r
497 &SmmFtwGetLastWriteHeader->Length,\r
498 &SmmFtwGetLastWriteHeader->PrivateDataSize,\r
499 (VOID *)SmmFtwGetLastWriteHeader->Data,\r
500 &SmmFtwGetLastWriteHeader->Complete\r
501 );\r
f3b80a8e 502 break;\r
503\r
504 default:\r
f3b80a8e 505 Status = EFI_UNSUPPORTED;\r
506 }\r
507\r
508 SmmFtwFunctionHeader->ReturnStatus = Status;\r
509\r
510 return EFI_SUCCESS;\r
511}\r
512\r
513\r
8a2d4996 514/**\r
515 SMM Firmware Volume Block Protocol notification event handler.\r
516 \r
517 @param[in] Protocol Points to the protocol's unique identifier\r
518 @param[in] Interface Points to the interface instance\r
519 @param[in] Handle The handle on which the interface was installed\r
520\r
521 @retval EFI_SUCCESS SmmEventCallback runs successfully\r
522 \r
523 **/\r
524EFI_STATUS\r
525EFIAPI\r
526FvbNotificationEvent (\r
527 IN CONST EFI_GUID *Protocol,\r
528 IN VOID *Interface,\r
529 IN EFI_HANDLE Handle\r
530 )\r
531{\r
532 EFI_STATUS Status;\r
533 EFI_SMM_FAULT_TOLERANT_WRITE_PROTOCOL *FtwProtocol;\r
f3b80a8e 534 EFI_HANDLE SmmFtwHandle;\r
8a2d4996 535 \r
536 //\r
537 // Just return to avoid install SMM FaultTolerantWriteProtocol again\r
538 // if SMM Fault Tolerant Write protocol had been installed.\r
539 // \r
540 Status = gSmst->SmmLocateProtocol (\r
541 &gEfiSmmFaultTolerantWriteProtocolGuid, \r
542 NULL, \r
543 (VOID **) &FtwProtocol\r
544 );\r
545 if (!EFI_ERROR (Status)) {\r
546 return EFI_SUCCESS;\r
547 }\r
548\r
549 //\r
550 // Found proper FVB protocol and initialize FtwDevice for protocol installation\r
551 //\r
f3b80a8e 552 Status = InitFtwProtocol (mFtwDevice);\r
8a2d4996 553 if (EFI_ERROR(Status)) {\r
554 return Status;\r
555 }\r
556 \r
557 //\r
558 // Install protocol interface\r
559 //\r
560 Status = gSmst->SmmInstallProtocolInterface (\r
f3b80a8e 561 &mFtwDevice->Handle,\r
8a2d4996 562 &gEfiSmmFaultTolerantWriteProtocolGuid,\r
563 EFI_NATIVE_INTERFACE,\r
f3b80a8e 564 &mFtwDevice->FtwInstance\r
8a2d4996 565 );\r
566 ASSERT_EFI_ERROR (Status); \r
f3b80a8e 567\r
568 //\r
569 // Notify the Ftw wrapper driver SMM Ftw is ready\r
570 //\r
571 SmmFtwHandle = NULL;\r
572 Status = gBS->InstallProtocolInterface (\r
573 &SmmFtwHandle,\r
574 &gEfiSmmFaultTolerantWriteProtocolGuid,\r
575 EFI_NATIVE_INTERFACE,\r
576 NULL\r
577 );\r
578 ASSERT_EFI_ERROR (Status);\r
8a2d4996 579 \r
580 return EFI_SUCCESS;\r
581}\r
582\r
f07268bd
SZ
583/**\r
584 SMM END_OF_DXE protocol notification event handler.\r
585 \r
586 @param Protocol Points to the protocol's unique identifier\r
587 @param Interface Points to the interface instance\r
588 @param Handle The handle on which the interface was installed\r
589\r
590 @retval EFI_SUCCESS SmmEndOfDxeCallback runs successfully\r
591\r
592**/\r
593EFI_STATUS\r
594EFIAPI\r
595SmmEndOfDxeCallback (\r
596 IN CONST EFI_GUID *Protocol,\r
597 IN VOID *Interface,\r
598 IN EFI_HANDLE Handle\r
599 )\r
600{\r
601 mEndOfDxe = TRUE;\r
602 return EFI_SUCCESS;\r
603}\r
8a2d4996 604\r
605/**\r
606 This function is the entry point of the Fault Tolerant Write driver.\r
607\r
608 @param[in] ImageHandle A handle for the image that is initializing this driver\r
609 @param[in] SystemTable A pointer to the EFI system table\r
610\r
611 @retval EFI_SUCCESS The initialization finished successfully.\r
612 @retval EFI_OUT_OF_RESOURCES Allocate memory error\r
613 @retval EFI_INVALID_PARAMETER Workspace or Spare block does not exist\r
614\r
615**/\r
616EFI_STATUS\r
617EFIAPI\r
618SmmFaultTolerantWriteInitialize (\r
619 IN EFI_HANDLE ImageHandle,\r
620 IN EFI_SYSTEM_TABLE *SystemTable\r
621 )\r
622{\r
623 EFI_STATUS Status;\r
f3b80a8e 624 EFI_HANDLE FtwHandle;\r
c219324c
ED
625 EFI_SMM_ACCESS2_PROTOCOL *SmmAccess;\r
626 UINTN Size;\r
f07268bd
SZ
627 VOID *SmmEndOfDxeRegistration;\r
628\r
8a2d4996 629 //\r
630 // Allocate private data structure for SMM FTW protocol and do some initialization\r
631 //\r
f3b80a8e 632 Status = InitFtwDevice (&mFtwDevice);\r
8a2d4996 633 if (EFI_ERROR(Status)) {\r
634 return Status;\r
635 }\r
c219324c
ED
636\r
637 //\r
638 // Get SMRAM information\r
639 //\r
640 Status = gBS->LocateProtocol (&gEfiSmmAccess2ProtocolGuid, NULL, (VOID **)&SmmAccess);\r
641 ASSERT_EFI_ERROR (Status);\r
642\r
643 Size = 0;\r
644 Status = SmmAccess->GetCapabilities (SmmAccess, &Size, NULL);\r
645 ASSERT (Status == EFI_BUFFER_TOO_SMALL);\r
646\r
647 Status = gSmst->SmmAllocatePool (\r
648 EfiRuntimeServicesData,\r
649 Size,\r
650 (VOID **)&mSmramRanges\r
651 );\r
652 ASSERT_EFI_ERROR (Status);\r
653\r
654 Status = SmmAccess->GetCapabilities (SmmAccess, &Size, mSmramRanges);\r
655 ASSERT_EFI_ERROR (Status);\r
656\r
657 mSmramRangeCount = Size / sizeof (EFI_SMRAM_DESCRIPTOR);\r
658\r
f07268bd
SZ
659 //\r
660 // Register EFI_SMM_END_OF_DXE_PROTOCOL_GUID notify function.\r
661 //\r
662 Status = gSmst->SmmRegisterProtocolNotify (\r
663 &gEfiSmmEndOfDxeProtocolGuid,\r
664 SmmEndOfDxeCallback,\r
665 &SmmEndOfDxeRegistration\r
666 );\r
667 ASSERT_EFI_ERROR (Status);\r
668\r
8a2d4996 669 //\r
670 // Register FvbNotificationEvent () notify function.\r
671 // \r
672 Status = gSmst->SmmRegisterProtocolNotify (\r
673 &gEfiSmmFirmwareVolumeBlockProtocolGuid,\r
674 FvbNotificationEvent,\r
675 &mFvbRegistration\r
676 );\r
677 ASSERT_EFI_ERROR (Status);\r
678\r
679 FvbNotificationEvent (NULL, NULL, NULL);\r
f3b80a8e 680\r
681 ///\r
682 /// Register SMM FTW SMI handler\r
683 ///\r
684 Status = gSmst->SmiHandlerRegister (SmmFaultTolerantWriteHandler, &gEfiSmmFaultTolerantWriteProtocolGuid, &FtwHandle);\r
685 ASSERT_EFI_ERROR (Status);\r
8a2d4996 686 \r
687 return EFI_SUCCESS;\r
688}\r