Skip to content

Releases: microsoft/mu_feature_mm_supv

v14.0.2

06 Nov 20:20
59d5aa0
Compare
Choose a tag to compare

What's Changed

  • Updated BASECORE override tags @kenlautner (#368)
    Change Details
      ## Description

    Updated Override tags to work with the latest MU_BASECORE release/202405 commit

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

    How This Was Tested

    Tested with CI

    Integration Instructions

    N/A




Full Changelog: v14.0.1...v14.0.2

v14.0.1

05 Nov 17:37
166c5e0
Compare
Choose a tag to compare

What's Changed

  • Updated OverrideValidation hashes for new basecore @apop5 (#364)
    Change Details
      ## Description

    Update the override validation for StandaloneMmPkg changes that were cherry-picked from edk2.

    No code changes are required, because the code changes were picked from a previous commit.

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

    How This Was Tested

    Local CI

    Integration Instructions

    N/A




  • Update override and tracking tags for StandaloneMmHobLib @kenlautner (#357)
    Change Details
      ## Description

    Basecore updated StandaloneMmHobLib so the relevant tags need to be updated.

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

    How This Was Tested

    Tested on physical platform. No issues seen.

    Integration Instructions

    N/A




🐛 Bug Fixes

  • Fix override tag @kenlautner (#360)
    Change Details
      ## Description

    The last override tag update accidentally added one that shouldn't be included in BaseLib.inf. This PR removes it.

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

    How This Was Tested

    Pipelines

    Integration Instructions

    N/A




Full Changelog: v14.0.0...v14.0.1

v14.0.0

01 Oct 18:55
eec362c
Compare
Choose a tag to compare

What's Changed

⚠️ Breaking Changes

  • Update override hash on PiSmmCore @kuqin12 (#349)
    Change Details
      ## Description

    Fixing an override hash failure from PiSmmCore

    For details on how to complete these options and their meaning refer to CONTRIBUTING.md.

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

    How This Was Tested

    This change was tested on Q35.

    Integration Instructions

    N/A

      </blockquote>
      <hr>
    </details>
    

🐛 Bug Fixes

  • Fixing MmRanges would pull in extra data from the next hob @kuqin12 (#337)
    Change Details
      ## Description

    Currently the MmRanges reported through initialization steps will be manipulated by the IPL code to extend the last entry to be an empty placeholder so that it will be populated during the ExecuteMmCoreFromMmram routine.

    However, the preemptively extended range will pull in extra data from the next hob, which could cause the rest of supervisor initialization to fault. This change fixed such issue by not overly copying data from hob.

    For details on how to complete to complete these options and their meaning refer to CONTRIBUTING.md.

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

    How This Was Tested

    This was tested on both QEMU Q35 and proprietary hardware platforms.

    Integration Instructions

    N/A

      </blockquote>
      <hr>
    </details>
    

🔐 Security Impacting

  • Update override hash on PiSmmCore @kuqin12 (#349)
    Change Details
      ## Description

    Fixing an override hash failure from PiSmmCore from:
    microsoft/mu_basecore@36f763d

    For details on how to complete these options and their meaning refer to CONTRIBUTING.md.

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

    How This Was Tested

    This change was tested on Q35.

    Integration Instructions

    N/A

      </blockquote>
      <hr>
    </details>
    

Full Changelog: v13.0.2...v14.0.0

v13.0.2

28 Aug 20:02
f12a1d5
Compare
Choose a tag to compare

What's Changed

  • Fix override from CodeQL and cherry-picks from latest basecore @kuqin12 (#331)
    Change Details
      ## Description

    This change updated the override validation tags. It also integrates the cherry-pick commit from microsoft/mu_basecore@4d722ac.

    For details on how to complete to complete these options and their meaning refer to CONTRIBUTING.md.

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

    How This Was Tested

    This was tested on pipeline and passed override check. Also booted on Q35 branch.

    Integration Instructions

    The change needs to pair with basecore commit microsoft/mu_basecore@4d722ac or later.

      </blockquote>
      <hr>
    </details>
    

Full Changelog: v13.0.1...v13.0.2

v13.0.1

08 Aug 23:02
6c121a3
Compare
Choose a tag to compare

What's Changed

  • Document update and version change @kuqin12 (#322)
    Change Details
      ## Description

    This change updates the version information of this package and module. It also updates the document on how to integrate the latest changes into platforms that are picking up 202405.

    The version number is updated from 11 to 13 to match the release version, which was missed in v12 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

    N/A

    Integration Instructions

    N/A




Full Changelog: v13.0.0...v13.0.1

v13.0.0

08 Aug 06:49
Compare
Choose a tag to compare

What's Changed

⚠️ Breaking Changes

  • [Rebase \& FF] [202405] 2405 integration for supervisor @kuqin12 (#321)
    Change Details
      ## Description

    This change integrates the upstream changes from 2405 release tag into supervisor

    • 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

    Change is tested on QEMU Q35 branch.

    Integration Instructions

    N/A




🔐 Security Impacting

  • [Rebase \& FF] [202405] 2405 integration for supervisor @kuqin12 (#321)
    Change Details
      ## Description

    This change integrates the upstream changes from 2405 release tag into supervisor

    • 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

    Change is tested on QEMU Q35 branch.

    Integration Instructions

    N/A




Full Changelog: v12.0.2...v13.0.0

v12.0.2

08 Aug 06:22
b250a39
Compare
Choose a tag to compare

What's Changed

🐛 Bug Fixes

  • Changed AllocatePageTableMemory to include a new variable @kenlautner (#317)
    Change Details
      ## Description

    Updated AllocatePageTableMemory to include a new input variable *NewAllocation. This variable is used to keep track of if new pages were allocated for use in the page table page pool. This fixes a bug where if we run out of page table pool pages while changing some pages memory attributes we'll recursively call into ConvertMemoryPageAttributes while allocating pages leading to unaccounted for pages in the original call. This leads to an assert by the ConvertMemoryPageAttributes 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

    Tested on two separate physical platforms that experienced the issue in different circumstances. This fix tested on those reproing platforms have the issue resolved and no longer saw any asserts.

    Integration Instructions

    N/A




🔐 Security Impacting

  • Changed AllocatePageTableMemory to include a new variable @kenlautner (#317)
    Change Details
      ## Description

    Updated AllocatePageTableMemory to include a new input variable *NewAllocation. This variable is used to keep track of if new pages were allocated for use in the page table page pool. This fixes a bug where if we run out of page table pool pages while changing some pages memory attributes we'll recursively call into ConvertMemoryPageAttributes while allocating pages leading to unaccounted for pages in the original call. This leads to an assert by the ConvertMemoryPageAttributes 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

    Tested on two separate physical platforms that experienced the issue in different circumstances. This fix tested on those reproing platforms have the issue resolved and no longer saw any asserts.

    Integration Instructions

    N/A




Full Changelog: v12.0.1...v12.0.2

v12.0.1

16 Jul 21:13
71049e8
Compare
Choose a tag to compare

What's Changed

  • Fixing override validation for basecore 2023110009.0.0. @apop5 (#315)
    Change Details
      ## Description

    Basecore 2023110009.0.0 included the change for consuming panic lib in place of CpuDeadloop.

    Replaced CpuDeadloops in MmSupervisorCore with calls to PanicLib.

    • 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

    Local CI.

    Integration Instructions

    N/A - Panic lib was already consumed in module.




  • Fixing override break due to PiSmmCpuDxeSmm updates. @apop5 (#307)
    Change Details
      ## Description

    PiSmmCpuDxeSmm was updated to use Panic library and Panic calls instead of CPU_DEADLOOPs for error conditions.
    This changed the generated override validation tag. mu_feature_mm_supv needed updated.

    The consumption of PanicLib was not introduced at this time. Details can be seen at link below:
     
    microsoft/mu_basecore@bbbff00

    • 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

    Local CI, and a mu_tiano_platforms build with newer version.

    Integration Instructions

    N/A




Full Changelog: v12.0.0...v12.0.1

v12.0.0

06 Jun 20:47
83b2f31
Compare
Choose a tag to compare

What's Changed

  • Various fixes caught by CLANG @kuqin12 (#303)
    Change Details
      # Preface

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

    Description

    This change will cover a few more CLANG fixes, including uninitialized variables and unintentionally pulled in compiler intrinsics.

    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 was tested on QEMU Q35.

    Integration Instructions

    N/A

      </blockquote>
      <hr>
    </details>
    
  • Fixing override validation failure by renaming gMpInformationHobGuid2 to gMpInformation2HobGuid @kuqin12 (#300)
    Change Details
      ## Description

    The pipeline build is broken due to a commit cherry-picked in to basecore: microsoft/mu_basecore@7f9a27e.

    This change is needed to unblock other PRs into this repo.

    • 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




Read more

v11.0.1

12 Apr 19:40
433d6dd
Compare
Choose a tag to compare

What's Changed

  • Update release version to v11 to match release versioning @kuqin12 (#280)
    Change Details
      ## Description

    We have not updated this field for too long, which will make the print out during runtime have discrepancy compared to the code release version. This change is made to fix that.

    • 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 only a version change, no functional update.

    Integration Instructions

    N/A




Full Changelog: v11.0.0...v11.0.1