Skip to content

v7.0.0
Compare
Choose a tag to compare
@github-actions github-actions released this 24 Apr 18:00
· 32 commits to refs/heads/main since this release
v7.0.0
2ec326c
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

  • Upgrade default QEMU to v9.0.0 @kuqin12 (#901)
    Change Details
      ## Description

    v9.0.0 fixed a few known issues blocking us from upgrading to QEMU of later than v7.2.0.

    This change is made to upgrade the default QEMU to v9.0.0 to intake the latest release.

    • 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 locally on Windows and WSL environment.

    Integration Instructions

    Existing clones will need to perform PlatformBuild.py --update to download the latest version of QEMU.



  • Integrate TF-A v2.10 @kuqin12 (#920)
    Change Details
      # Preface

    Please ensure you have read the contribution docs prior
    to submitting the pull request. In particular,
    pull request guidelines.

    Description

    The TF-A v2.10 updated the footprint of images drastically and supported extra CPU models, causing the existing flash map not able to suit the BL1.

    This change updated the flash map and improved the patching routine in post-build to fail the build next time.

    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 functional on QEMU SBSA with max CPU model.

    Integration Instructions

    N/A

      </blockquote>
  <hr>
</details>
  • Refresh Paging Audit Test App CI Exemption @TaylorBeebe (#919)
    Change Details
      ## Description

    The DXE paging audit test app was updated to check for Enhanced Memory
    Protection compliance. Project Mu is currently being updated to pass to
    pass the remaining two checks (RP on free memory and RP on GCD
    nonexistent regions). This PR updates the exemption date for
    SBSA and Q35 so test failures don't block CI gates.

    • 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 CI pipelines

    Integration Instructions

    N/A



  • qemu\_extdep: Remove the linux extdep @Javagedes (#915)
    Change Details
      ## Description

    Removes the qemu external dependency for linux and instead uses the qemu that is directly installed on the system.

    Note: I've opted to keep the github action that produces the linux external dependency in-case we opt to switch back to using it, or as an example to anyone that needs to build it locally.

    • 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

    N/A

    Integration Instructions

    N/A

      </blockquote>
  <hr>
</details>
  • Enable MU Debugger Package for Q35 \& SBSA @cfernald (#910)
    Change Details
      ## 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.

    • 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

      </blockquote>
  <hr>
</details>

⚠️ Breaking Changes

  • Update MU\_BASECORE to v2023110004.0.0, MM\_SUPV to v11.0.1 and MU\_PLUS to v2023110000.0.5 @kuqin12 (#911)
    Change Details
      ## 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
    • 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 QEMU Q35 and SBS, both platforms booted to UEFI shell.

    Integration Instructions

    N/A



🛠️ Submodule Updates

  • Bump Features/DEBUGGER from `6fa8e9f` to `aed4cc3` @dependabot (#924)
    Change Details
      Bumps [Features/DEBUGGER](https://github.com/microsoft/mu_feature_debugger) from `6fa8e9f` to `aed4cc3`.
    Commits
    • aed4cc3 Add workaround for windbg trying to read windows shared data page (#21)
    • aa1ff35 Fix CodeQL issue for delimiter index in GDB parsing (#20)
    • f138aa3 GitHub Action: Bump robinraju/release-downloader from 1.9 to 1.10 (#19)
    • 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 MU\_BASECORE from 2023110005.0.0 to 2023110005.0.1 @ProjectMuBot (#922)
    Change Details
      Bumps MU_BASECORE from `2023110005.0.0` to `2023110005.0.1`

    Introduces 1 new commits in MU_BASECORE.

    Commits
    • f26f86 Bug: Fix incorrect CodeQL fix - REBASE with PR 6024 (#818)

    Signed-off-by: Project Mu Bot mubot@microsoft.com



  • Bump MU\_BASECORE from 2023110004.0.0 to 2023110005.0.0 @ProjectMuBot (#921)
    Change Details
      Bumps MU_BASECORE from `2023110004.0.0` to `2023110005.0.0`

    Introduces 11 new commits in MU_BASECORE.

    Commits
    • d6e011 CryptoPkg/BaseCryptLib: add DigestLen to RsaOaepEncrypt(), RsaOaepDecrypt() (#797)
    • 718ec9 CryptoPkg/Binaries: update to 2023.11.3 (#805)
    • 291b63 Add ARM and AARCH64 MSCVC Support to StackCheckLib (#808)
    • e2ef21 .gitattributes: Prevent line ending conversion (#809)
    • b28d62 DscCompleteCheck: Bugfix ignorepaths config option (#806)
    • 8c89cc Repo File Sync: Update to Mu DevOps 9.1.9 and Rust 1.76.0 (#804)
    • 24d560 Repo File Sync: Update to Ubuntu Container 0e124c1 (#810)
    • f5c010 GitHub Action: Bump robinraju/release-downloader from 1.9 to 1.10 (#811)
    • bb4782 Repo File Sync: synced file(s) with microsoft/mu_devops (#812)
    • 398875 [CHERRY-PICK] MdePkg/SmBios.h: Add New ProcessorFamily definitions for SMBIOS Type4 (#813)
    • 6e49e9 GitHub Action: Bump robinraju/release-downloader from 1.9 to 1.10 (#817)

    Signed-off-by: Project Mu Bot mubot@microsoft.com



  • Bump Features/DEBUGGER from `e462d5a` to `6fa8e9f` @dependabot (#917)
    Change Details
      Bumps [Features/DEBUGGER](https://github.com/microsoft/mu_feature_debugger) from `e462d5a` to `6fa8e9f`.
    Commits
    • 6fa8e9f Clarify launching windbgx from command line using provided config (#18)
    • 17806a9 Repo File Sync: synced file(s) with microsoft/mu_devops (#17)
    • a19f52d GitHub Action: Bump microsoft/setup-msbuild from 1.3 to 2 (#15)
    • e0cc235 GitHub Action: Bump robinraju/release-downloader from 1.9 to 1.10 (#16)
    • a22af04 Repo File Sync: Update to Ubuntu Container 0e124c1 (#14)
    • 9485d65 Repo File Sync: Update to Mu DevOps 9.1.9 (#13)
    • 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)

Full Changelog: v6.0.0...v7.0.0

Contributors

cfernald, Javagedes, and 4 other contributors
Assets 9