## Description
Updates release pipeline for the qemu binary to release qemu v7.2.0 as a
external dependency and to also provide the following roms:
- efi-e1000e.rom
- efi-virtio.rom
- [ ] 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, ...
- [ ] 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, ...
- [ ] 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, ...
## How This Was Tested
Verified Terminal was not in an invalid state after exiting qemu, and
that the above roms were successfully found at runtime.
## Integration Instructions
Perform a release and update the qemu external dependency inside
mu_tiano_platforms
## Description
The e1000 NIC is useful for OS debugging and general "real
hardware"-like network access.
- [x] Impacts functionality?
- [ ] Impacts security?
- [ ] Breaking change?
- [ ] Includes tests?
- [ ] Includes documentation?
## How This Was Tested
N/A
## Integration Instructions
N/A
## Description
The Instruction Set Extension, specifically SSE4.2, is standard and used
by Windows. This adds it to the default QEMU configuration for Q35.
- [X] Impacts functionality?
- [ ] Impacts security?
- [ ] Breaking change?
- [ ] Includes tests?
- [ ] Includes documentation?
## How This Was Tested
Tested local Windows boot.
## Integration Instructions
N/A
## 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.
- [x] 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, ...
- [ ] 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, ...
- [ ] 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, ...
## How This Was Tested
Tested by booting SBSA and observing the improved boot time.
## Integration Instructions
N/A
## Description
The StackCheckLib instances have been updated in all subrepos. Thi PR
updates all subrepos and the StackCheckLib instances for SBSA and Q35.
- [x] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [x] 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, ...
- [ ] 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, ...
- [ ] 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, ...
## How This Was Tested
Tested in pipelines
## Integration Instructions
N/A
## 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, ...
- [ ] 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, ...
- [ ] 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, ...
## 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
Bumps Common/MU_TIANO from `2023110000.0.2` to `2023110000.0.3`
Introduces 1 new commits in
[Common/MU_TIANO](https://github.com/microsoft/mu_tiano_plus.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
## Description
Add a new workflow that will build and prepare qemu binaries for both
Windows and Linux. This workflow has three triggers:
1. A pull request to the main branch, which will only trigger when
either the workflow itself, or the qemu version file is updated. This
workflow will upload the binaries as an artifact to the workflow.
2. A release, which will upload the binaries as an artifact to the
associated release
3. A manual trigger, which allows for testing the workflow on a custom
branch. This will upload the binaries as an artifact to the workflow.
- [ ] 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, ...
- [ ] 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, ...
- [ ] 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, ...
## How This Was Tested
A release was performed using this github action on a personal branch
([v0.1.9](https://github.com/Javagedes/mu_tiano_platforms/releases/tag/v0.1.9)),
and was used as an external dependency on a mu_tiano_platforms [Draft
PR](https://github.com/microsoft/mu_tiano_platforms/pull/851), which is
passing, and will be merged once this PR has been merged and a release
has been executed.
## Integration Instructions
N/A
## Description
Links the non-NULL instance of DxeHash2CryptoLib to QemuQ35Pkg and
QemuSbsaPkg so the Hash 2 Service Binding protocol is installed.
This can be used as a dynamic hashing interface by other modules.
- [x] 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, ...
- [ ] 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, ...
- [ ] 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, ...
## How This Was Tested
Verified Hash 2 Service Binding protocol is installed by MuCryptoDxe.
## Integration Instructions
N/A
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
## Description
- Updates QemuQ35Pkg to use the RT DXE shared crypto driver and use
the RuntimeDxeCryptLib instance for RT DXE drivers.
- Removes a binary VariableRuntimeDxe EFI image checked in (with
crypto statically linked) that was an intermediate solution while
RT DXE shared crypto was developed.
- Updates paths that refer to shared crypto use the build variable
`SHARED_CRYPTO_PATH` that is set by the ext dep. This allows the
path to resolve to the ext dep regardless of where it is placed
in the code tree.
- 960ebde updated QemuQ35Pkg to resolve DSC parser warnings for a
suspicious expression comparison warning. This change also fixes
the warning for QemuSbsaPkg.
Updates some Mu submodules to their latest releases. The MU_BASECORE
update is required for these changes.
- **MU_BASECORE:
[v2023110001.0.1](https://github.com/microsoft/mu_basecore/releases/tag/v2023110001.0.1)
(76b62eb)**
- CryptoPkg/RuntimeDxeCryptLib: Make globals static
- BaseTools/GenFds: Resolve absolute workspace INF paths
- **MU_BASECORE:
[v2023110001.0.0](https://github.com/microsoft/mu_basecore/releases/tag/v2023110001.0.0)
(0dd0d48)**
- CryptoPkg/Driver: Remove directory
- .pytool/Plugin/DscCompleteCheck: Allow git ignore syntax
- pip: update edk2-pytool-library requirement from ~=0.21.2 to ~=0.21.3
- CryptoPkg: Add RT DXE shared crypto library instance
- Remove static initialization of gMmst for MM Core Lib
- Repo File Sync: Improve inline documentation in CodeQL workflow
- pip: update edk2-pytool-library requirement from ~=0.20.0 to ~=0.21.2
- Repo File Sync: synced file(s) with microsoft/mu_devops
- **Common/MU:
[v2023110000.0.1](https://github.com/microsoft/mu_plus/releases/tag/v2023110000.0.1)
(c3b9b01)**
- pip: bump edk2-pytool-library from 0.21.2 to 0.21.3
- remove edk2-basetools
- Remove AdvancedLogger MmCoreArm dependence on global variables.
- Switch MmCoreArm advanced logger to use updated MMU functions
- Repo File Sync: Improve inline documentation in CodeQL workflow
- pip: bump edk2-pytool-library from 0.20.0 to 0.21.2
- Repo File Sync: synced file(s) with microsoft/mu_devops
- **Common/MU_TIANO:
[v2023110000.0.2](https://github.com/microsoft/mu_tiano_plus/releases/tag/v2023110000.0.2)
(f7e2628)**
- pip: bump edk2-pytool-library from 0.21.2 to 0.21.3
- remove edk2-basetools
---
- [x] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [x] 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, ...
- [ ] 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, ...
- [ ] 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, ...
## How This Was Tested
- QemuQ35Pkg SMM and SMM_DISABLED build and boot to EFI shell and
Windows OS
- QemuSbsaPkg boot to EFI shell
## Integration Instructions
N/A - Affects crypto used in this repo.
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Bumps Common/MU_TIANO from `2023110000.0.0` to `2023110000.0.1`
Introduces 4 new commits in
[Common/MU_TIANO](https://github.com/microsoft/mu_tiano_plus.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
## Description
This change updates all submodules to point to 202311 based MU
submodules.
Code change specifically applicable to QEMU Q35:
dea6002d6e24e6daa2bc12d3d60f51
Specifically, the submodules are updated to:
| Submodule | Version |
| - | - |
| MU_BASECORE | v2023110000.0.1 |
| MU_PLUS | v2023110000.0.0 |
| MU_OEM_SAMPLE | v2023110000.0.0 |
| MU_TIANO_PLUS | v2023110000.0.0 |
| MM_SUPV | v9.0.0 |
| MU_SILICON_ARM | v2023110000.0.0 |
- [x] 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, ...
- [x] 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, ...
- [ ] 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, ...
## How This Was Tested
This branch was tested on QEMU Q35 and verified bootable to UEFI shell
and Windows OS.
## Integration Instructions
N/A
---------
Co-authored-by: Michael Kubacki <michael.kubacki@microsoft.com>
## Description
Add section to debugging.md about using GDB for QEMU debugger and move
to common debugging file.
- [ ] Impacts functionality?
- [ ] Impacts security?
- [ ] Breaking change?
- [ ] Includes tests?
- [X] Includes documentation?
## How This Was Tested
N/A
## Integration Instructions
N/A
Bumps Features/DFCI from `4.0.3` to `4.0.4`
Introduces 16 new commits in
[Features/DFCI](https://github.com/microsoft/mu_feature_dfci).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
## Description
defines SMM_CRYPTO_ARCH in QemuQ35Pkg.dsc to resolve parser warnings
regarding suspicious expressions that occur because $(SMM_CRYPTO_ARCH)
is not replaced with a value (because a value is not defined).
Prints multiple of the following parser warning:
```cmd
INFO - Parser...
INFO - c:\src\mu_tiano_platforms\MU_BASECORE\CryptoPkg\Driver\Bin\Crypto.pcd.TINY_SHA.inc.dsc(112): warning: Suspicious expression: == Comparison between Operand of string type and Boolean/Number Type always return False.
INFO - !if $(SMM_CRYPTO_ARCH) == X64
```
- [ ] 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, ...
- [ ] 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, ...
- [ ] 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, ...
## How This Was Tested
Built with and without SMM_CRYPTO_ARCH being defined, and verified the
parser warning was removed when it was defined.
## Integration Instructions
N/A
Bumps Common/MU_TIANO from `2023020000.2.0` to `2023020000.2.1`
Introduces 1 new commits in
[Common/MU_TIANO](https://github.com/microsoft/mu_tiano_plus.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
## Description
Moving forward the OpenSSL submodule will no longer be present in
`CryptoPkg` and the only option to integrate crypto into the platform
will be shared crypto (via the binary crypto ext dep).
The option to enable/disable shared crypto is removed since disabling
it is no longer an option.
Notes:
- Integrates newly available `AARCH64` PEI and Standalone MM shared
crypto binaries.
- The `BaseCryptLibUnitTest` EFI shell test is removed since it depends
on
functions not present in the PPI/Protocol instances of `BaseCryptLib`
and
the crypto releases should have the tests run before the release is
made.
- An issue to track this is here:
https://github.com/microsoft/mu_crypto_release/issues/56
- Runtime DXE crypto is not currently available. It is only needed at
this time for
the non-SMM instance of `QemuQ35Pkg` (`VariableRuntimeDxe`). Since this
is not the
primary target for `QemuQ35Pkg`, the Runtime DXE binary will be updated
in the
future to unblock Mu Basecore updates in Mu Tiano Platforms.
- An issue to track that is here:
https://github.com/microsoft/mu_crypto_release/issues/55
---
Updates these submodules to the following release points:
- `MU_BASECORE`:
[v2023020013.1.0](https://github.com/microsoft/mu_basecore/releases/tag/v2023020013.1.0)
- `Common/MU_TIANO`:
[v2023020000.2.0](https://github.com/microsoft/mu_tiano_plus/releases/tag/v2023020000.2.0)
- `Features/MM_SUPV`:
[v8.1.8](https://github.com/microsoft/mu_feature_mm_supv/releases/tag/v8.1.8)
---
- [x] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [x] 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, ...
- [ ] 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, ...
- [ ] 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, ...
## How This Was Tested
- `QemuQ35Pkg` and `QemuSbsaPkg` CI build and boot.
## Integration Instructions
- These changes only affect mu_tiano_platforms.
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Bumps Common/MU from `2023020006.1.0` to `2023020006.1.1`
Introduces 7 new commits in
[Common/MU](https://github.com/microsoft/mu_plus.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
## Description
Updates edk2-pytool-extensions to v0.27.0 and edk2-pytool-library to
v0.20.0, which moves Edk2DB away from using sqlite3 directly, instead
using a ORM to manage the database schema and querying functionlity.
Applies the necessary changes to convert Edk2DB querying from raw SQL
queries to sqlalchemy (ORM) queries.
- [ ] 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, ...
- [ ] 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, ...
- [ ] 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, ...
## How This Was Tested
PlatformTest for QemuQ35Pkg and QemuSbsaPkg continues to work, and
produces the same information.
## Integration Instructions
N/A
Bumps Common/MU_TIANO from `2023020000.1.2` to `2023020000.1.3`
Introduces 10 new commits in
[Common/MU_TIANO](https://github.com/microsoft/mu_tiano_plus.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Bumps Common/MU from `2023020006.0.0` to `2023020006.1.0`
Introduces 8 new commits in
[Common/MU](https://github.com/microsoft/mu_plus.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Updates Standalone MM modules to use the `BaseCryptLibOnProtocolPpi/StandaloneMmCryptLib.inf`
instance of `BaseCryptLib`. This will allow those modules to use the `gEdkiiSmmCryptoProtocolGuid`
protocol instance published by the Standalone MM crypto binary.
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Introduces 9 new commits in
[MU_BASECORE](https://github.com/microsoft/mu_basecore.git).
In particular, this release updates the shared crypto binary external
dependency in CryptoPkg to include the Standalone MM binaries.
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
## Description
The DXE paging audit test app was updated to check for Enhanced Memory
Protection compliance. Project Mu is currently being updated to pass to
the currently failing checks. This PR updates the exemption date for
SBSA and Q35 so test failures don't block CI gates.
- [x] 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, ...
- [ ] 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, ...
- [ ] 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, ...
## How This Was Tested
Tested in pipelines
## Integration Instructions
N/A
## Description
Adds commits that only applied Uncrustify formatting or converted
line endings to a .git-blame-ignore-revs file so they are ignored
by git blame. This is supported by GitHub:
https://github.blog/changelog/2022-03-24-ignore-commits-in-the-blame-view-beta/
This helps clean up git blame by filtering out these changes.
Note: This file needs to be updated on rebase branches. Processes
like filter-branch can automatically update relevant SHAs.
---
Commits cover `OvmfPkg`. Although the package no longer exists, it is
still in
the history of many files in derived packages.
- [ ] 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, ...
- [ ] 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, ...
- [ ] 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, ...
## How This Was Tested
- `git blame`
## Integration Instructions
N/A
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Bumps Common/MU from `2023020004.1.1` to `2023020006.0.0`
Introduces 12 new commits in
[Common/MU](https://github.com/microsoft/mu_plus.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Bumps MU_BASECORE from `2023020009.0.3` to `2023020010.0.0`
Introduces 8 new commits in
[MU_BASECORE](https://github.com/microsoft/mu_basecore.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Joey Vagedes
dependabot[bot]
Project Mu UEFI Bot [bot]
Chris Fernald
Taylor Beebe
Project Mu Bot [bot]
Doug Flick
Project Mu Bot
Michael Kubacki
kuqin12