release-v2024050003.0.0

What's Changed

• Update shared crypto to v1.0.1 @makubacki (#1247)
  
  Change Details

    ## Description

  Includes a change to fix the conditional syntax in Standalone MM include FDF files.

  • Impacts functionality?
  • Impacts security?
  • Breaking change?
  • Includes tests?
  • Includes documentation?
  • Backport to release branch?

  How This Was Tested

  • Local build and CI
  • Integration on a platform that uses shared crypto (and Standalone MM shared crypto)

  Integration Instructions

  • No changes from v1.0.0 integration instructions
    

  
  

  ---

• Createa Mock for PciRootBridgeIoProtocol, MockPciPlatformProtocol \& add mock function under MockUefiBootServiceTableLib @v-boscochen (#1213)
  
  Change Details

    ## Description

  Add mock functions under MockUefiBootServiceTableLib , and Create Mock for PciRootBridgeIoProtocol

  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?
  • Backport to release branch?

  How This Was Tested

  Unit tests component can call these mock functions success

  Integration Instructions

  N/A

    </blockquote>
    <hr>
  </details>
  

• BaseTools: Disable Second DLINK step for WHOLEARCHIVE @os-d (#1243)
  
  Change Details

    ## Description

  Project Mu does not use WHOLEARCHIVE, due to issues in silicon partner code when it is enabled. In order to support WHOLEARCHIVE, edk2 added a second dlink step in the build rules to get the benefit of identifying duplicate symbols without needing the space expansion. This is an extra linking step for each module and so does increase build time. Without WHOLEARCHIVE, this is an unneeded step on Mu, so it is disabled here.

  This additional linking step just is a test to verify that there are not duplicate symbols, the actual FW build is not changed here, that is what the second DLINK step does, without the DLINK2_FLAGS where WHOLEARCHIVE is set. HOST_APPLICATIONs still require WHOLEARCHIVE for the actual build, as GoogleTest requires it or could miss some unit tests, due to the complexities of a C++ build in the edk2 build system. UnitTestFrameworkPkgHost.dsc.inc sets this in the DLINK_FLAGS, not DLINK2_FLAGS, so this is still respected.

  • Impacts functionality?
  • Impacts security?
  • Breaking change?
  • Includes tests?
  • Includes documentation?
  • Backport to release branch?

  How This Was Tested

  CI build

  Integration Instructions

  N/A.

    </blockquote>
    <hr>
  </details>
  

• Create Mock for SafeIntLib @TsunFeng (#1235)
  
  Change Details

    ## Description

  Create Mock for SafeIntLib

  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?
  • Backport to release branch?

  How This Was Tested

  Unit tests component can call these mock functions success

  Integration Instructions

  N/A

    </blockquote>
    <hr>
  </details>
  

• Add mock for protocol MockFirmwareVolumeBlock under MdePkg @Rasheed-Yusuf (#1216)
  
  Change Details

    ## Description

  Add Mock for Firmware Volume Block Protocol in MdePkg

  Signed-off-by: rasheed yusuf [email protected]
  Cc: Maintainer Shruti Gupta [email protected]
  Cc: Reviewer Shruti Gupta [email protected]

  • Impacts functionality?
  • Impacts security?
  • Breaking change?
  • Includes tests?
  • Includes documentation?
  • Backport to release branch?

  How This Was Tested

  Consumed in a GoogleTest

  Integration Instructions

  N/A
  

  
  

  ---

  
  

• Add Mock for Mock Smm Sw Dispatch2 Protocol @Rasheed-Yusuf (#1217)
  
  Change Details

    ## Description

  Add Mock for Mock Smm Sw Dispatch2 Protocol

  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?
  • Backport to release branch?

  How This Was Tested

  Incorporated into GoogleTest

  Integration Instructions

  N/A
  

  
  

  ---

  
  

⚠️ Breaking Changes

• Update shared crypto to v1.0.0 @makubacki (#1245)
  
  Change Details

    ## Description

  Major Changes:

  • Note: Shared Crypto now follows straightforward semantic versioning. The version number is incremented based on the type of changes made to the shared crypto binaries. The version number is not tied to the version of the underlying crypto provider.

  • Note: Prior to adopting semantic versioning in the 1.0.0 release, the version number followed a form of YYYY.MM.PATCH. The 1.0.0 release was the first to use semantic versioning and proceeds any of those versions.

  ---

  See https://github.com/microsoft/mu_crypto_release/releases/tag/v1.0.0 for the detailed set of changes.

  ---

  • Impacts functionality?
  • Impacts security?
  • Breaking change?
  • Includes tests?
  • Includes documentation?
  • Backport to release branch?

  How This Was Tested

  • Use shared crypto ext dep on a platform already using it
  • Integration on a X64 MM Supervisor Standalone MM platform
  • Integration on a X64 non-MM Supervisor Standalone MM platform

  Integration Instructions

  Breaking Change - Standalone MM Integration

  Two options are now provided for Standalone MM. It is important to select the option based on the Standalone MM core used on your platform:

  • StandaloneMmPkg
    • Use STANDALONEMM_CRYPTO_SERVICES
  • MmSupervisorPkg
    • Use STANDALONEMM_MMSUPV_CRYPTO_SERVICES

  Since the MM Supervisor currently does not support AARCH64, only a X64 MM Supervisor Standalone MM binary is available. A platform should not have both STANDALONEMM_CRYPTO_SERVICES and STANDALONEMM_MMSUPV_CRYPTO_SERVICES set to non-NONE values.
  

  
  

  ---

  
  

Full Changelog: dev-v2024050002.0.0...v2024050003.0.0