Skip to content

v7.0.1
Compare
Choose a tag to compare
@github-actions github-actions released this 17 May 01:30
· 104 commits to refs/heads/main since this release
v7.0.1
f4f0027
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

What's Changed

  • Add `bochs` VGA binary to QEMU release @kuqin12 (#950)
    Change Details
      ## Description

    This change added an extra binary from QEMU builds to support QEMU-SBSA platform graphic operations.

    • 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 by running QEMU-SBSA with the platform release UEFI binaries and booted to UEFI shell properly.

    Integration Instructions

    N/A



  • Add Advanced Logger PRM to Q35 @os-d (#935)
    Change Details
      ## Description

    The Advanced Logger PRM was added to Advanced Logger. This PR gives an example of integrating it and using it.

    • 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.



  • Add NETWORK\_ENABLE option @makubacki (#940)
    Change Details
      ## Description

    Simplifies network enabling by using a dedicated flag for enabling.

    Preserves existing behavior where networking is disabled by default.

    Networking was hardcoded to off in the QemuSbsaPkg runner, that is
    not modified in this change.

    • 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

    • Run without flag set and verify networking is disabled.
    • Run with flag and verify networking is enabled.

    Integration Instructions

    N/A



  • Use MdeModulePkg BaseRngLibTimerLib instance @makubacki (#939)
    Change Details
      ## Description

    The BaseRngLibTimerLib instance was moved to MdeModulePkg as noted in
    https://bugzilla.tianocore.org/show_bug.cgi?id=4504.

    That move was made because some algorithm GUIDs were added to the
    GetRngGuid() interface that were not in the UEFI Specification.

    tianocore/edk2@e934684
    adds a deprecation message to the older MdePkg instance.

    This change updates all paths in this repo to use the MdeModulePkg
    instance.

    • Impacts functionality?
    • Impacts security?
    • Breaking change?
    • Includes tests?
    • Includes documentation?

    How This Was Tested

    • QemuQ35Pkg and QemuSbsaPkg built and boot to EFI shell

    Integration Instructions

    N/A



  • Update QEMU external dependency @kuqin12 (#926)
    Change Details
      ## Description

    The latest QEMU v9.0.0 is updated in the platform release v7.0.0. This change is to pick it up.

    • 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 change is tested on QEMU Q35 as well as SBSA and booted to UEFI shell.

    Integration Instructions

    N/A



🐛 Bug Fixes

  • Added exception handling when `GetConsoleMode` API fails @kuqin12 (#929)
    Change Details
      ## Description

    This change fixes a pipeline break after moving to QEMU v9.0.0 by adding a try-except routine to handle the case on the server builds.

    • 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 change was tested locally and on the pipeline build.

    Integration Instructions

    N/A



🔐 Security Impacting

  • Integrate EFI\_MEMORY\_RP on Free Memory Updates @TaylorBeebe (#931)
    Change Details
      ## Description

    mu_basecore and mu_silicon_tiano_arm submodules have been updated to support EFI_MEMORY_RP on free memory which will cause accesses to unallocated or freed memory to trigger a page fault and target one of the most common programmer errors.

    This memory protection feature is configurable via the DXE memory protection settings.

    • 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 to Windows on Q35, booting to shell on SBSA, and running the DxePagingAuditTestApp.

    Integration Instructions

    N/A



🛠️ Submodule Updates

  • Bump Features/DEBUGGER from `6f04dea` to `b923b3b` @dependabot (#948)
    Change Details
      Bumps [Features/DEBUGGER](https://github.com/microsoft/mu_feature_debugger) from `6f04dea` to `b923b3b`.
    Commits
    • b923b3b Introduce a fixed copy of the GDB scripts (#30)
    • d38fbc2 Repo File Sync: .gitattributes: Prevent line ending conversion (#27)
    • 9e9c38a Expand Windbgx work around for 0 page reads. (#26)
    • See full diff in compare view

    You can trigger a rebase of this PR by commenting @dependabot rebase.

    Dependabot commands and options

    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)
  • Bump Common/MU\_OEM\_SAMPLE from 2023110000.0.1 to 2023110000.0.2 @ProjectMuBot (#947)
    Change Details
      Bumps Common/MU_OEM_SAMPLE from `2023110000.0.1` to `2023110000.0.2`

    Introduces 13 new commits in Common/MU_OEM_SAMPLE.

    Commits
    • e57f11 pip: update edk2-pytool-extensions requirement from ~=0.27.2 to ~=0.27.3 (#197)
    • 39dfc5 pip: update edk2-pytool-library requirement from ~=0.21.3 to ~=0.21.4 (#200)
    • 0c3e22 Repo File Sync: prevent `rustup` from self-updating (#201)
    • f18293 pip: update edk2-pytool-library requirement from ~=0.21.4 to ~=0.21.5 (#202)
    • c83e0a Repo File Sync: Update to Mu DevOps 9.1.9 (#203)
    • 0eb0b3 Repo File Sync: Update to Ubuntu Container 0e124c1 (#204)
    • fd16af GitHub Action: Bump robinraju/release-downloader from 1.9 to 1.10 (#205)
    • a89862 Repo File Sync: synced file(s) with microsoft/mu_devops (#206)
    • 5a098b pip: bump regex from 2023.12.25 to 2024.4.16 (#207)
    • b5bf4b GitHub Action: Bump robinraju/release-downloader from 1.9 to 1.10 (#208)
    • 506b8e pip: bump regex from 2024.4.16 to 2024.4.28 (#209)
    • 7ee8c3 pip: update edk2-pytool-extensions requirement from ~=0.27.3 to ~=0.27.4 (#210)
    • 6cd87e OemPkg: DfciDeviceIdSupportLib: Fixing uninitialized variable being used (#211)

    Signed-off-by: Project Mu Bot [email protected]



  • Bump Features/DEBUGGER from `cee0d1a` to `6f04dea` @dependabot (#937)
    Change Details
      Bumps [Features/DEBUGGER](https://github.com/microsoft/mu_feature_debugger) from `cee0d1a` to `6f04dea`.
    Commits
    • 6f04dea Remove windbg breakpoint workaround & improvements (#25)
    • d86d50e pip: update edk2-pytool-extensions requirement from ~=0.27.3 to ~=0.27.4 (#24)
    • See full diff in compare view

    You can trigger a rebase of this PR by commenting @dependabot rebase.

    Dependabot commands and options

    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)
  • Bump Features/DEBUGGER from 0.1.1 to 0.1.2 @ProjectMuBot (#932)
    Change Details
      Bumps Features/DEBUGGER from `0.1.1` to `0.1.2`

    Introduces 2 new commits in Features/DEBUGGER.

    Commits
    • 8b3082 Improvements to Windbgx integration and UEFI extension (#22)
    • cee0d1 Improvements to UEFIExt and fix register writes (#23)

    Signed-off-by: Project Mu Bot [email protected]



  • Bump Common/MU from 2023110000.0.5 to 2023110000.0.6 @ProjectMuBot (#930)
    Change Details
      Bumps Common/MU from `2023110000.0.5` to `2023110000.0.6`

    Introduces 3 new commits in Common/MU.

    Commits
    • cd7ce3 Relax report length requirements (#455)
    • e6308e GitHub Action: Bump robinraju/release-downloader from 1.9 to 1.10 (#472)
    • da051c Moving the global variable from header file into library instances (#473)

    Signed-off-by: Project Mu Bot [email protected]



Full Changelog: v7.0.0...v7.0.1

Contributors

makubacki, os-d, and 4 other contributors
Assets 9
Loading