## Description
Update mu_basecore to top of release/202405 and supervisor repo to pair
up with the updated override tags.
For details on how to complete to complete these options and their
meaning refer to
[CONTRIBUTING.md](https://github.com/microsoft/mu/blob/HEAD/CONTRIBUTING.md).
- [x] Impacts functionality?
- [ ] Impacts security?
- [ ] Breaking change?
- [ ] Includes tests?
- [ ] Includes documentation?
## How This Was Tested
Tested on QEMU Q35 and booted to shell.
## Integration Instructions
N/A
Bumps
[Features/DEBUGGER](https://github.com/microsoft/mu_feature_debugger)
from `d7db129` to `ad7047d`.
<details>
<summary>Commits</summary>
<ul>
<li><a
href="ad7047d100"><code>ad7047d</code></a>
pip: update edk2-pytool-extensions requirement from ~=0.27.10 to
~=0.27.11 (<a
href="https://redirect.github.com/microsoft/mu_feature_debugger/issues/51">#51</a>)</li>
<li>See full diff in <a
href="d7db129716...ad7047d100">compare
view</a></li>
</ul>
</details>
<br />
You can trigger a rebase of this PR by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
</details>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps
[Features/DEBUGGER](https://github.com/microsoft/mu_feature_debugger)
from `c9efe78` to `d7db129`.
<details>
<summary>Commits</summary>
<ul>
<li><a
href="d7db129716"><code>d7db129</code></a>
Repo File Sync: synced file(s) with microsoft/mu_devops (<a
href="https://redirect.github.com/microsoft/mu_feature_debugger/issues/50">#50</a>)</li>
<li><a
href="312b83662f"><code>312b836</code></a>
pip: update edk2-pytool-library requirement from ~=0.21.9 to ~=0.21.10
(<a
href="https://redirect.github.com/microsoft/mu_feature_debugger/issues/49">#49</a>)</li>
<li><a
href="3553982820"><code>3553982</code></a>
pip: bump antlr4-python3-runtime from 4.13.1 to 4.13.2 (<a
href="https://redirect.github.com/microsoft/mu_feature_debugger/issues/48">#48</a>)</li>
<li><a
href="4de89c0a27"><code>4de89c0</code></a>
pip: update edk2-pytool-library requirement from ~=0.21.8 to ~=0.21.9
(<a
href="https://redirect.github.com/microsoft/mu_feature_debugger/issues/47">#47</a>)</li>
<li>See full diff in <a
href="c9efe78878...d7db129716">compare
view</a></li>
</ul>
</details>
<br />
You can trigger a rebase of this PR by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
</details>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Aaron <105021049+apop5@users.noreply.github.com>
## Description
The Project Mu submodules have moved to release/202405 and as the final
step in qualifying that, we move mu_tiano_platforms to the new
submodules. Below is the list of major changes for this repo to
accommodate the new submodules:
SBSA Dropping ArmVirtPkg Dependency
--
QemuSbsaPkg was dependent on ArmVirtPkg for two libraries and a set of
device tree PCDs. These device tree PCDs were moved to OvmfPkg in edk2,
which we do not carry in Project Mu. In general, ArmVirtPkg allows
dependencies on OvmfPkg, which makes it not a good candidate for Project
Mu to depend on. The PCDs were moved to QemuSbsaPkg, QemuVirtMemInfoLib
was copied there, and the HobLib was pointed to the mu_basecore version,
as the ArmVirtPkg version was not needed, thus breaking the dependency
on ArmVirtPkg. Some other ArmVirtPkg unused PCDs were dropped entirely.
MM_SUPV Updates
--
There were a lot of MM_SUPV updates in release/202405, which led to
needing to copy an instance of SmmRelocationLib from OvmfPkg to
QemuQ35Pkg. There was debt from previous integrations where changes from
MmFeatureLib were not picked up, which were required to work with the
new supervisor.
SourceLevelDebugPkg Dropped
--
Project Mu no longer carries SourceLevelDebugPkg, so all references and
hooks were dropped from the repo.
Non-NX Compat Images Allowed to be Loaded
--
Previously, on Windows built FW's, we would block loading non-NX compat
binaries. This prevents booting most modern Linuxes as shim/grub do not
have the NX_COMPAT flag set for released versions. This was changed to
not block loading non-NX Compat images so that Linux can boot on
Q35/SBSA on Windows.
SBSA Qemu run without SME and SVE
--
Similar to requiring SSE support on Q35, Windows and Linux have started
using SVE instructions on ARM64. However, TF-A in the SP_MM
configuration does not support SME or SVE instructions, so TF-A would
crash when one of those instructions occurred. Qemu is now configured to
run without support for SME and SVE so that the OSes do not attempt to
use them. It was also discovered that Qemu 9.0.2 or newer is required
for booting an OS on SBSA now, it is not clear what changed.
Cleanups and Old References Dropped
--
- As part of debugging some of the changes needed for release/202405,
some DSC cleanups were made.
- MemoryOverrideBinLib was not carried forward to release/202405, so it
was dropped from DSCs.
- AdvLoggerAccessLibNull is used for VariableStandaloneMmLib.inf in
QemuSbsaPkg now instead of the actual instance, as we are not using
AdvLogger there.
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?
- **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, ...
- [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
Booted Q35 and SBSA to Windows and Linux
## Integration Instructions
Qemu 9.0.2 is required for Linux builds to boot into an OS now, it is
unclear exactly what is broken with older versions.
---------
Co-authored-by: Kun Qin <kuqin@microsoft.com>
## Description
Produces an RNG PPI that is used by shared crypto to abstract platform
RNG support.
- Updates Mu Basecore to v2023110010.0.1
- Updates Mu Tiano Plus to v2023110001.1.0
- Updates Mu MM Supervisor to v12.0.1 (for overrides)
- Updates pytools for compat with Mu Basecore Rust plugin
- [ ] Impacts functionality?
- [ ] Impacts security?
- [ ] Breaking change?
- [ ] Includes tests?
- [ ] Includes documentation?
## How This Was Tested
- CI
- Verified RngPei is launched
- Verified RNG PPI is installed
- Verified Shared Crypto's RNG PPI dependency is met
- EFI Shell Boot
## Integration Instructions
- N/A
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Bumps
[Features/DEBUGGER](https://github.com/microsoft/mu_feature_debugger)
from `b160742` to `c61ca5b`.
<details>
<summary>Commits</summary>
<ul>
<li><a
href="c61ca5bc0d"><code>c61ca5b</code></a>
pip: update edk2-pytool-extensions requirement from ~=0.27.6 to ~=0.27.9
(<a
href="https://redirect.github.com/microsoft/mu_feature_debugger/issues/45">#45</a>)</li>
<li>See full diff in <a
href="b160742deb...c61ca5bc0d">compare
view</a></li>
</ul>
</details>
<br />
You can trigger a rebase of this PR by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
</details>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Aaron <105021049+apop5@users.noreply.github.com>
# Preface
Please ensure you have read the [contribution
docs](https://github.com/microsoft/mu/blob/master/CONTRIBUTING.md) prior
to submitting the pull request. In particular,
[pull request
guidelines](https://github.com/microsoft/mu/blob/master/CONTRIBUTING.md#pull-request-best-practices).
## Description
This change is created to support building SBSA using CLANGPDB.
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?
- **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
This was tested locally using QEMU SBSA platform and booted to UEFI
shell.
## Integration Instructions
N/A
Bumps MU_BASECORE from `2023110007.1.0` to `2023110008.0.0`
Introduces 21 new commits in
[MU_BASECORE](https://github.com/microsoft/mu_basecore.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Co-authored-by: Michael Kubacki <michael.kubacki@microsoft.com>
Bumps Features/DFCI from `4.0.5` to `4.0.6`
Introduces 18 new commits in
[Features/DFCI](https://github.com/microsoft/mu_feature_dfci).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
## Description
This change updates the MU_BASECORE, MM_SUPV and MU_PLUS submodules and
fixes integration errors:
| Submodule | Version |
| - | - |
| MU_BASECORE | v2023110004.0.0 |
| MM_SUPV | v11.0.1 |
| MU_PLUS | v2023110000.0.5 |
- [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 was tested on QEMU Q35 and SBS, both platforms booted to UEFI
shell.
## Integration Instructions
N/A
---------
Co-authored-by: Aaron <105021049+apop5@users.noreply.github.com>
Co-authored-by: Oliver Smith-Denny <osde@microsoft.com>
## Description
Ingests the MU_FEATURE_DEBUGGER repo and enabled the software debugger
for both Q35 and SBSA through the build flag
`BLD_*_DEBUGGER_ENABLED=TRUE` to debug over the serial port specified by
the runtime flag `SERIAL_PORT=####`.
Creates a debug transport for Q35 that wraps the IO port serial port lib
implementation but swaps the UART port address before calling to allow
the debugger to run on a separate port then the debug output.
- [X] Impacts functionality?
- [ ] Impacts security?
- [ ] Breaking change?
- [ ] Includes tests?
- [ ] Includes documentation?
## How This Was Tested
Locally tested on both SBSA and Q35.
## Integration Instructions
N/A
## Description
The MU_BASECORE update changed the hash used in MmSupervisorPkg. This
change updated both submodules to fix the auto-PRs build break.
- [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
Q35 platform is tested with QEMU 9.0.0-rc1 on Windows and booted to UEFI
shell.
## 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
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>
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
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 Features/DFCI from `4.0.2` to `4.0.3`
Introduces 2 new commits in
[Features/DFCI](https://github.com/microsoft/mu_feature_dfci).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
## Description
All submodules have been updated to top of tree to ingest the stack
cookie library transition commits. The packages in this repo were
updated to use the new stack cookie library.
- [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 on Q35 and SBSA
## Integration Instructions
N/A
Bumps Features/CONFIG from `2.0.0` to `2.0.2`
Introduces 15 new commits in
[Features/CONFIG](https://github.com/microsoft/mu_feature_config.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Co-authored-by: Michael Kubacki <michael.kubacki@microsoft.com>
## Description
Updates the repo for a change that merged UefiCpuLib with CpuLib.
UefiCpuLib will be removed entirely soon so all references are updated
to CpuLib.
Includes the following submodule updates:
- `MU_BASECORE` to `v2023020005.0.1`
- `Common/MU` to `v2023020001.4.1`
- `Common/MU_TIANO` to `v2023020001.4.1`
- `Features/MM_SUPV` to `v8.1.5`
---
- [ ] 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
- CI package build (via PR checks)
## Integration Instructions
N/A
---
Associated Changes in Submodules
- https://github.com/microsoft/mu_feature_mm_supv/pull/164
- https://github.com/microsoft/mu_plus/pull/304
- https://github.com/microsoft/mu_tiano_plus/pull/174
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Bumps Features/DFCI from `4.0.0` to `4.0.1`
Introduces 9 new commits in
[Features/DFCI](https://github.com/microsoft/mu_feature_dfci).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Bumps Features/MM_SUPV from `8.1.1` to `8.1.2`
Introduces 1 new commit in
[Features/MM_SUPV](https://github.com/microsoft/mu_feature_mm_supv.git).
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
dependabot[bot]
kuqin12
Project Mu Bot [bot]
Oliver Smith-Denny
Michael Kubacki
Chris Fernald
Taylor Beebe