forked from tianocore/edk2
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Sync patches r14454, r14455, r14456, r14457, r14458, and r14462 from …
…main trunk. 1. MdeModulePkg: Variable drivers robustly handle crashes during Reclaim(). 2. SecurityPkg: Variable drivers robustly handle crashes during Reclaim(). 3. Nt32Pkg: Use FaultTolerantWritePei driver. 4. EmulatorPkg: Use FaultTolerantWritePei driver. 5. OvmfPkg EmuVariableFvbRuntimeDxe: Let FaultTolerantWriteDxe to init working block header. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Jeff Fan <[email protected]> git-svn-id: https://svn.code.sf.net/p/edk2/code/branches/UDK2010.SR1@15341 6f19259b-4bc3-4df7-8a09-765794883524
- Loading branch information
Showing
31 changed files
with
1,588 additions
and
539 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,54 @@ | ||
/** @file | ||
Define the GUID gEdkiiFaultTolerantWriteGuid that will be used to build | ||
FAULT_TOLERANT_WRITE_LAST_WRITE_DATA GUID hob and install PPI to inform the check | ||
for FTW last write data has been done. The GUID hob will be only built if FTW last write was | ||
still in progress with SpareComplete set and DestinationComplete not set. | ||
Copyright (c) 2013, Intel Corporation. All rights reserved.<BR> | ||
This program and the accompanying materials are licensed and made available under | ||
the terms and conditions of the BSD License that accompanies this distribution. | ||
The full text of the license may be found at | ||
http://opensource.org/licenses/bsd-license.php. | ||
THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS, | ||
WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED. | ||
**/ | ||
|
||
#ifndef _FAULT_TOLERANT_WRITE_H_ | ||
#define _FAULT_TOLERANT_WRITE_H_ | ||
|
||
#define EDKII_FAULT_TOLERANT_WRITE_GUID \ | ||
{ \ | ||
0x1d3e9cb8, 0x43af, 0x490b, { 0x83, 0xa, 0x35, 0x16, 0xaa, 0x53, 0x20, 0x47 } \ | ||
} | ||
|
||
// | ||
// FTW Last write data. It will be used as gEdkiiFaultTolerantWriteGuid GUID hob data. | ||
// | ||
typedef struct { | ||
/// | ||
/// Target address to be updated in FTW last write. | ||
/// | ||
EFI_PHYSICAL_ADDRESS TargetAddress; | ||
/// | ||
/// Spare address to back up the updated buffer. | ||
/// | ||
EFI_PHYSICAL_ADDRESS SpareAddress; | ||
/// | ||
/// The length of data that have been backed up in spare block. | ||
/// It is also the length of target block that has been erased. | ||
/// | ||
UINT64 Length; | ||
} FAULT_TOLERANT_WRITE_LAST_WRITE_DATA; | ||
|
||
// | ||
// This GUID will be used to install PPI to inform the check for FTW last write data has been done. | ||
// The related FAULT_TOLERANT_WRITE_LAST_WRITE_DATA GUID hob will be only built if | ||
// FTW last write was still in progress with SpareComplete set and DestinationComplete not set. | ||
// It means the target buffer has been backed up in spare block, then target block has been erased, | ||
// but the target buffer has not been writen in target block from spare block. | ||
// | ||
extern EFI_GUID gEdkiiFaultTolerantWriteGuid; | ||
|
||
#endif |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.