Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Adding customizable GUID for BERT extra variables support (#122)
## Description Current implement will allow extra variables with names specified under `PcdBertEntriesVariableNames` and namespace GUID being `gEfiHardwareErrorVariableGuid` to be collected into BERT table for OS consumption. However, variables under `gEfiHardwareErrorVariableGuid` has certain restrictions that does not allow random variable names to be used and could potentially clash with `HwErrRec####` occupied by other firmware entities. This change will add the flexibility for the platform to specify their own variable GUID to be collected during boot for BERT table usage. For each item, place an "x" in between `[` and `]` if true. Example: `[x]`. _(you can also check items in the GitHub UI)_ - [x] Impacts functionality? - [ ] Impacts security? - [ ] Breaking change? - [ ] Includes tests? - [ ] Includes documentation? ## How This Was Tested Tested on QEMU virtual systems and proprietary physical devices. ## Integration Instructions For platforms that need to support specific CPER formatted variables coalition into the BERT table, one should override the PCD value of `gMsWheaPkgTokenSpaceGuid.PcdBertEntriesVariableGuid` of their choices. Otherwise, `gEfiHardwareErrorVariableGuid` will be the default value and certain variable naming schema might restrict the specific use case.
- Loading branch information
1 parent
7f4c330
commit 2dd19af
Showing
3 changed files
with
43 additions
and
7 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