v5.1.1
What's Changed
-
Add E1000 rom to QEMU ext dep @cfernald (#874)
Change Details
## Description
The e1000 NIC is useful for OS debugging and general "real hardware"-like network access.
- Impacts functionality?
- Impacts security?
- Breaking change?
- Includes tests?
- Includes documentation?
How This Was Tested
N/A
Integration Instructions
N/A
</blockquote> <hr> </details>
-
Add SSE4.2 to q35 QEMU runner CPU features @cfernald (#873)
Change Details
## Description
The Instruction Set Extension, specifically SSE4.2, is standard and used by Windows. This adds it to the default QEMU configuration for Q35.
- Impacts functionality?
- Impacts security?
- Breaking change?
- Includes tests?
- Includes documentation?
How This Was Tested
Tested local Windows boot.
Integration Instructions
N/A
</blockquote> <hr> </details>
-
Set PcdFixedDebugPrintErrorLevel in QemuSbsaPkg to Improve Boot Time @TaylorBeebe (#871)
Change Details
## Description
There's a large slowdown during GCD sync when the syncing logic debug dumps the GCD map thousands of times. I updated the syncing logic to skip the dump process if the GCD debug verbosity level is not set. Checking the verbosity is done via a call to DebugPrintLevelEnabled() in DebugLib which checks the fixed debug print PCD.
This PR sets the FixedAtBuild PCD to be the same as the PatchableInModule PCD so the map dump function is skipped.
- Impacts functionality?
- Functionality - Does the change ultimately impact how firmware functions?
- Examples: Add a new library, publish a new PPI, update an algorithm, ...
- Impacts security?
- Security - Does the change have a direct security impact on an application,
flow, or firmware? - Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- Security - Does the change have a direct security impact on an application,
- Breaking change?
- Breaking change - Will anyone consuming this change experience a break
in build or boot behavior? - Examples: Add a new library class, move a module to a different repo, call
a function in a new library class in a pre-existing module, ...
- Breaking change - Will anyone consuming this change experience a break
- Includes tests?
- Tests - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- Includes documentation?
- Documentation - Does the change contain explicit documentation additions
outside direct code modifications (and comments)? - Examples: Update readme file, add feature readme file, link to documentation
on an a separate Web page, ...
- Documentation - Does the change contain explicit documentation additions
How This Was Tested
Tested by booting SBSA and observing the improved boot time.
Integration Instructions
N/A
</blockquote> <hr> </details>
- Impacts functionality?
-
Use qemu external dependency @Javagedes (#851)
Change Details
## Description
Use an external dependency for qemu rather than relying on it being installed by the user.
- Impacts functionality?
- Functionality - Does the change ultimately impact how firmware functions?
- Examples: Add a new library, publish a new PPI, update an algorithm, ...
- Impacts security?
- Security - Does the change have a direct security impact on an application,
flow, or firmware? - Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- Security - Does the change have a direct security impact on an application,
- Breaking change?
- Breaking change - Will anyone consuming this change experience a break
in build or boot behavior? - Examples: Add a new library class, move a module to a different repo, call
a function in a new library class in a pre-existing module, ...
- Breaking change - Will anyone consuming this change experience a break
- Includes tests?
- Tests - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- Includes documentation?
- Documentation - Does the change contain explicit documentation additions
outside direct code modifications (and comments)? - Examples: Update readme file, add feature readme file, link to documentation
on an a separate Web page, ...
- Documentation - Does the change contain explicit documentation additions
How This Was Tested
Ensured Boot to shell and Boot to windows using the Windows and Linux qemu external dependencies. Verified TPM Replay functionality continued to work as expected.
Integration Instructions
N/A
</blockquote> <hr> </details>
- Impacts functionality?
🔐 Security Impacting
-
Update Subrepos to Sync Stack Cookie Changes @TaylorBeebe (#870)
Change Details
## Description
The StackCheckLib instances have been updated in all subrepos. Thi PR updates all subrepos and the StackCheckLib instances for SBSA and Q35.
- Impacts functionality?
- Functionality - Does the change ultimately impact how firmware functions?
- Examples: Add a new library, publish a new PPI, update an algorithm, ...
- Impacts security?
- Security - Does the change have a direct security impact on an application,
flow, or firmware? - Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- Security - Does the change have a direct security impact on an application,
- Breaking change?
- Breaking change - Will anyone consuming this change experience a break
in build or boot behavior? - Examples: Add a new library class, move a module to a different repo, call
a function in a new library class in a pre-existing module, ...
- Breaking change - Will anyone consuming this change experience a break
- Includes tests?
- Tests - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- Includes documentation?
- Documentation - Does the change contain explicit documentation additions
outside direct code modifications (and comments)? - Examples: Update readme file, add feature readme file, link to documentation
on an a separate Web page, ...
- Documentation - Does the change contain explicit documentation additions
How This Was Tested
Tested in pipelines
Integration Instructions
N/A
</blockquote> <hr> </details>
- Impacts functionality?
🛠️ Submodule Updates
-
Bump MU\_BASECORE from 2023110001.0.2 to 2023110001.1.0 @ProjectMuBot (#865)
Change Details
Bumps MU_BASECORE from `2023110001.0.2` to `2023110001.1.0`
Introduces 5 new commits in MU_BASECORE.
Commits
Signed-off-by: Project Mu Bot [email protected]
-
[Rebase \&\& FF] Bump MU\_BASECORE from 2023110001.0.1 to 2023110001.0.2 @ProjectMuBot (#858)
Change Details
Bumps MU_BASECORE from `2023110001.0.1` to `2023110001.0.2`
Introduces 1 new commits in MU_BASECORE.
Signed-off-by: Project Mu Bot [email protected]
-
Bump Common/MU\_TIANO from 2023110000.0.2 to 2023110000.0.3 @ProjectMuBot (#862)
Change Details
Bumps Common/MU_TIANO from `2023110000.0.2` to `2023110000.0.3`
Introduces 1 new commits in Common/MU_TIANO.
Signed-off-by: Project Mu Bot [email protected]
-
Bump Features/CONFIG from 2.0.8 to 2.0.9 @ProjectMuBot (#863)
Change Details
Bumps Features/CONFIG from `2.0.8` to `2.0.9`
Introduces 7 new commits in Features/CONFIG.
Commits
- 3aee7a Repo File Sync: synced file(s) with microsoft/mu_devops (#311)
- 10bbb1 pip: bump edk2-pytool-extensions from 0.27.0 to 0.27.2 (#313)
- c60f58 pip: bump edk2-pytool-library from 0.20.0 to 0.21.2 (#312)
- 8415b1 Repo File Sync: Improve inline documentation in CodeQL workflow (#314)
- e0c8db remove edk2-basetools (#315)
- b673c3 pip: bump edk2-pytool-library from 0.21.2 to 0.21.3 (#316)
- cca9d2 Reset ConIn on ConfApp entrypoint (#317)
Signed-off-by: Project Mu Bot [email protected]
Full Changelog: v5.1.0...v5.1.1