Bumps Common/MU_OEM_SAMPLE from `2023110000.0.2` to `2024050000.0.0`
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Co-authored-by: Aaron <105021049+apop5@users.noreply.github.com>
## Description
This change re-enables the memory map test app fix by picking up the
latest MU_PLUS and MU_SILICON_ARM.
Resolves https://github.com/microsoft/mu_tiano_platforms/issues/1017.
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?
- [x] Includes tests?
- [ ] Includes documentation?
## How This Was Tested
This change is tested on QEMU Q35.
## Integration Instructions
N/A
## 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
The DxePagingAuditTestApp was failing on all architectures because of a
misimplementation. That was fixed in
https://github.com/microsoft/mu_plus/pull/528. This patch pulls in the
newer mu_plus to get that change and drops the exemption from Q35 and
SBSA.
- [ ] 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, ...
- [x] 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
Ran paging audit test and it succeeds.
## Integration Instructions
N/A.
# 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 Common/MU from `2023110001.0.0` to `2023110001.0.1`
Introduces 8 new commits in
[Common/MU](https://github.com/microsoft/mu_plus.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Bumps Common/MU_TIANO from `2023110000.0.5` to `2023110000.1.0`
Introduces 17 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_OEM_SAMPLE from `2023110000.0.1` to `2023110000.0.2`
Introduces 13 new commits in
[Common/MU_OEM_SAMPLE](https://github.com/microsoft/mu_oem_sample.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
## Description
The Advanced Logger PRM was added to Advanced Logger. This PR gives an
example of integrating it and using it.
- [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 Q35 to Windows and fetching the log via the variable
interface and the PRM interface and confirming the log is the same.
## Integration Instructions
Follow this example to integrate into another platform.
## 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>
Bumps Common/MU from `2023110000.0.3` to `2023110000.0.4`
Introduces 3 new commits in
[Common/MU](https://github.com/microsoft/mu_plus.git).
<details>
<summary>Commits</summary>
<ul>
<li><a
href="968f75bcb6">968f75</a>
MfciDxe: Indicate the MFCI Protocol is produced in the INF (<a
href="https://github.com/microsoft/mu_plus/pull/454">#454</a>)</li>
<li><a
href="1f3a8e1ebd">1f3a8e</a>
pip: bump edk2-pytool-library from 0.21.4 to 0.21.5 (<a
href="https://github.com/microsoft/mu_plus/pull/456">#456</a>)</li>
<li><a
href="c35b46f622">c35b46</a>
When recovering Pei buffer from hob list, need to fix internal pointe…
(<a href="https://github.com/microsoft/mu_plus/pull/457">#457</a>)</li>
</ul>
</details>
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Co-authored-by: kuqin12 <42554914+kuqin12@users.noreply.github.com>
## Description
The PDE.dat file is no longer produced by the paging audit, so the
get_file call will fail.
- [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 running the paging audit on Q35 and SBSA
## 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
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
- 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>
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>
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>
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 Common/MU from `2023020004.0.5` to `2023020004.1.0`
Introduces 1 new commits in
[Common/MU](https://github.com/microsoft/mu_plus.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Bumps Common/MU from `2023020004.0.4` to `2023020004.0.5`
Introduces 4 new commits in
[Common/MU](https://github.com/microsoft/mu_plus.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Bumps Common/MU from `2023020004.0.3` to `2023020004.0.4`
Introduces 2 new commits in
[Common/MU](https://github.com/microsoft/mu_plus.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
# Description
A recent mu_plus commit splits MemoryProtectionTestApp into SMM and
DXE versions. Now that they are split, we can run the DXE version of the test
on SBSA. This PR adds the new test instances and adds the DXE test to the
SBSA CI pipelines.
- [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 the CI pipelines
## Integration Instructions
N/A
## Description
Use secureboot binary blobs generated from
https://github.com/microsoft/secureboot_objects for the PK, KeK, Db,
Dbx, and 3PDb. The secureboot binary blobs are downloaded as an external
dependency, which enables the contents of the secureboot variables to be
strongly versioned and easily tracked.
This change uses a new version of SecureBootKeyStoreLib (from
MsCorePkg), which consumes the secureboob binary values from PCDs and a
new helper plugin (BuildSecurebootPcds) generates these PCDs on each
build.
- [ ] 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
Verified QemuPkg and QemuSbsaPkg continue to boot and can have
secureboot enabled.
## Integration Instructions
N/A
Bumps Common/MU from `2023020003.4.0` to `2023020004.0.0`
Introduces 1 new commits in
[Common/MU](https://github.com/microsoft/mu_plus.git).
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 Common/MU_TIANO from `2023020000.1.1` to `2023020000.1.2`
Introduces 12 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 `2023020003.2.2` to `2023020003.3.0`
Introduces 3 new commits in
[Common/MU](https://github.com/microsoft/mu_plus.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Bumps Common/MU from `2023020003.2.1` to `2023020003.2.2`
Introduces 2 new commits in
[Common/MU](https://github.com/microsoft/mu_plus.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Bumps Common/MU from `2023020003.2.0` to `2023020003.2.1`
Introduces 5 new commits in
[Common/MU](https://github.com/microsoft/mu_plus.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
## Description
Adds a new library instance for QEMU platforms that allows a TPM
Replay event log to optionally be passed from the QEMU command
line.
See
https://github.com/microsoft/mu_plus/tree/HEAD/TpmTestingPkg/TpmReplayPei#input-channel-fw_cfg
for more information about passing a TPM Replay log through the
FW CFG interface.
For reference, this readme has additional TPM Replay information:
https://github.com/microsoft/mu_tiano_platforms/blob/main/Platforms/Docs/Q35/Features/feature_tpm_replay.md
- [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
- Passed FW CFG TPM event log through QemuQ35Pkg
- Verified library integrated without a log being passed uses
lower priority input channels as expected
## Integration Instructions
N/A - The new input channel library instance for TPM Replay is
integrated
in this change.
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Bumps Common/MU_TIANO from `2023020000.1.0` to `2023020000.1.1`
Introduces 18 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 `2023020003.0.0` to `2023020003.0.1`
Introduces 2 new commits in
[Common/MU](https://github.com/microsoft/mu_plus.git).
<details>
<summary>Commits</summary>
<ul>
<li><a
href="16d600a0d5">16d600</a>
pip: bump edk2-pytool-extensions from 0.25.0 to 0.25.1 (<a
href="https://github.com/microsoft/mu_plus/pull/343">#343</a>)</li>
<li><a
href="0033f8e82d">0033f8</a>
Add HiiKeyboardLayout crate to support UEFI HII Keyboard Layouts (<a
href="https://github.com/microsoft/mu_plus/pull/342">#342</a>)</li>
</ul>
</details>
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Co-authored-by: Taylor Beebe <31827475+TaylorBeebe@users.noreply.github.com>
Bumps Common/MU from `2023020002.1.0` to `2023020003.0.0`
Introduces 3 new commits in
[Common/MU](https://github.com/microsoft/mu_plus.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Bumps Common/MU from `2023020002.0.4` to `2023020002.1.0`
Introduces 1 new commits in
[Common/MU](https://github.com/microsoft/mu_plus.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
## Description
Per integration instructions in
https://github.com/microsoft/mu_plus/pull/324,
`UsbMouseAbsolutePointerDxe` is removed and `UsbHidDxe` and `UefiHidDxe`
are
added to the build.
The absolute pointer protocol will now be installed by the
`AbsolutePointer`
crate in `HidPkg` linked against the `UefiHidDxe` module.
- [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 QemuQ35Pkg and QemuSbsaPkg build and boot to EFI shell
## Integration Instructions
N/A
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Bumps Common/MU from `2023020002.0.1` to `2023020002.0.2`
Introduces 15 new commits in
[Common/MU](https://github.com/microsoft/mu_plus.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Project Mu Bot [bot]
kuqin12
Oliver Smith-Denny
Taylor Beebe
Michael Kubacki
Joey Vagedes
Project Mu Bot