## Description
On Linux, I build QEMU images with various features enabled. To more
easily enable users to use a custom QEMU image, this change
introduces a new variable `QEMU_PATH` that will override the default
executable used from the system path if provided.
- [ ] 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 packages with `QEMU_PATH` present and not present.
## Integration Instructions
N/A - Instructions for usage are in Platforms/Docs/Common/building.md
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 MU_BASECORE from `2023020007.2.0` to `2023020007.2.1`
Introduces 2 new commits in
[MU_BASECORE](https://github.com/microsoft/mu_basecore.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 MU_BASECORE from `2023020007.1.3` to `2023020007.2.0`
Introduces 4 new commits in
[MU_BASECORE](https://github.com/microsoft/mu_basecore.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Add PanicLib to Qemu35Pkg and QemuSbsaPkg so it is available for an
upcoming Mu Basecore update that requires the library.
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
## Description
Add this scope so Rust related CI plugins run since the packages are
already building Rust code.
- [ ] 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 CI builds with the scope set
## Integration Instructions
N/A - Affects plugins run in this repo
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Bumps MU_BASECORE from `2023020007.1.1` to `2023020007.1.2`
Introduces 1 new commits in
[MU_BASECORE](https://github.com/microsoft/mu_basecore.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
Since there's a couple build variables that can influence which front
page is built and how it is loaded, this change updates the currently
empty front page feature document to include the relevant build
variable information.
- [ ] 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, ...
- [x] 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 build including markdownlint.
## Integration Instructions
N/A
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
1. `MU_BASECORE` updated to `v2023020007.1.1`
- Improved debug messages.
2. `Silicon/Arm/MU_TIANO` updated to `v2023020000.1.0`
- Updates to the PEIM that produces the
Memory Type Info HOB to not place non-RT types in the HOB. This
allows the Memory Type Info UEFI variable to be updated per the
expectations in the Memory Type Info variable check lib in
MdeModulePkg.
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
This repo has historically not cared about impacting the sizes of
runtime memory buckets.
To help track changes, particularly those that are from dependencies
used by other repos, this change enables reset of memory type info
changes.
The idea being that this will help determine when changes modify the
memory bucket allocations in a significant way so the information can
be communicated to platform owners that do care about bucket sizes
and they can plan accordingly.
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Updates the default values for `PcdMemoryTypeEfiACPIReclaimMemory`
and `PcdMemoryTypeEfiReservedMemoryType` to prevent a runtime
adjustment to the memory bucket sizes.
Based on the values calculated including buffer:
- `*` value modified and used in memory type info
- `X` value is not used in memory type info
Memory Previous Current Minimum Next
Type Pages Pages Pages Pages
====== ======== ======== ======== =======
09 00000000 00000021 00000000 00000029[*]
0A 00000000 00000000 00000000 00000000
00 00000000 00000404 00000000 00000505[*]
06 00000258 00000192 00000000 00000258
05 00000190 00000186 00000000 00000190
03 000005DC 000005DB 00000000 000005DC[X]
04 00002EE0 00002C77 00000000 00002EE0[X]
01 00000014 00000000 00000000 00000014[X]
02 00000000 00000000 00000000 00000000[X]
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Updates the default values for `PcdMemoryTypeEfiACPIReclaimMemory`
and `PcdMemoryTypeEfiReservedMemoryType` to prevent a runtime
adjustment to the memory bucket sizes.
Based on the values calculated including buffer:
Memory Previous Current Minimum Next
Type Pages Pages Pages Pages
====== ======== ======== ======== =======
0A 00000080 00000026 00000000 00000080
09 00000010 00000012 00000000 00000016*
00 00000080 0000040D 00000000 00000510*
05 00000100 000000AF 00000000 00000100
06 00000100 00000100 00000000 00000100
Memory Type Information settings change.
Signed-off-by: Michael Kubacki <michael.kubacki@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>
Adds the library instance in UefiTestingPkg to QemuQ35Pkg and
QemuSbsaPkg to support building DxePagingAuditTestApp.
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Bumps Silicon/Arm/MU_TIANO from `2023020000.0.6` to `2023020000.0.7`
Introduces 16 new commits in
[Silicon/Arm/MU_TIANO](https://github.com/microsoft/mu_silicon_arm_tiano.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Bumps MU_BASECORE from `2023020007.0.0` to `2023020007.1.0`
Introduces 5 new commits in
[MU_BASECORE](https://github.com/microsoft/mu_basecore.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Bumps MU_BASECORE from `2023020006.3.1` to `2023020007.0.0`
Introduces 3 new commits in
[MU_BASECORE](https://github.com/microsoft/mu_basecore.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
## Description
Current script will try to update the mcopy configuration file. After
QEMU run, the build script will then try to open the virtual disk
indicated in this configuration. When there are multiple building
instances on the same Linux system, we could end up with various
conflicts, either opening up the incorrect image file, or opened up a
file from other build jobs.
This change attempts to fix it by initiating a configuration file for
each build for reference and update the environment variable to set up
the configuration.
- [ ] 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 on both selfhost agents internal and here on the public
pipeline builds.
## Integration Instructions
N/A.
---------
Co-authored-by: Michael Kubacki <michael.kubacki@microsoft.com>
Bumps Common/MU from `2023020001.5.0` to `2023020001.5.1`
Introduces 10 new commits in
[Common/MU](https://github.com/microsoft/mu_plus.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
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>
# 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
There has been build failures observed on selfhosted pipelines running
on AARCH64 systems. It was due to the rust setup we recently added.
The failure on the surface was because the build process will try to
install x86_64 toolchain on AARCH64 systems. This change will remove the
extra steps for selfhosted agent runs as those environments should be
preset properly.
For each item, place an "x" in between `[` and `]` if true. Example:
`[x]`.
_(you can also check items in the GitHub UI)_
- [ ] 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 is tested on both internal and external pipelines.
## Integration Instructions
N/A
Bumps Common/MU_OEM_SAMPLE from `2023020000.0.5` to `2023020000.0.6`
Introduces 15 new commits in
[Common/MU_OEM_SAMPLE](https://github.com/microsoft/mu_oem_sample.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Bumps [xmlschema](https://github.com/sissaschool/xmlschema) from 2.4.0
to 2.5.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/sissaschool/xmlschema/releases">xmlschema's
releases</a>.</em></p>
<blockquote>
<h2>v2.5.0 (2023-09-21)</h2>
<ul>
<li>Fix identity keys tracking with additional full XPath checks on XML
data</li>
<li>Rewrite schema exports using relative paths</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/sissaschool/xmlschema/blob/master/CHANGELOG.rst">xmlschema's
changelog</a>.</em></p>
<blockquote>
<h1><code>v2.5.0</code>_ (2023-09-21)</h1>
<ul>
<li>Fix identity keys tracking with additional full XPath checks on XML
data</li>
<li>Rewrite schema exports using relative paths</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="05af170a3f"><code>05af170</code></a>
Fix weak filepaths in test_pl_validation_translation</li>
<li><a
href="11f4b43943"><code>11f4b43</code></a>
Add pyproject.toml</li>
<li><a
href="9d8963c880"><code>9d8963c</code></a>
Merge and fix translation tests module</li>
<li><a
href="785dbea128"><code>785dbea</code></a>
Update release info</li>
<li><a
href="eac7eb06dc"><code>eac7eb0</code></a>
Detach schema export as a function in a new module</li>
<li><a
href="866ed43587"><code>866ed43</code></a>
Fix schema export on MacOS and Windows</li>
<li><a
href="ff1a6489dc"><code>ff1a648</code></a>
Update CI and Tox config</li>
<li><a
href="ea3967af6f"><code>ea3967a</code></a>
Bump minor release</li>
<li><a
href="16cfd1bd6b"><code>16cfd1b</code></a>
Fix style and static typing errors</li>
<li><a
href="3a83e9fd47"><code>3a83e9f</code></a>
Replace exported locations with relative paths (issue <a
href="https://redirect.github.com/sissaschool/xmlschema/issues/362">#362</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/sissaschool/xmlschema/compare/v2.4.0...v2.5.0">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
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>
Michael Kubacki
dependabot[bot]
Project Mu Bot [bot]
Project Mu UEFI Bot [bot]
Project Mu Bot
Michael Kubacki
kuqin12