v2025020002.0.2

What's Changed

• [TPM][FF-A] Add Yield to FF-A Library @Raymond-MS (#1532)
  
  Change Details

    ## Description

  Add the FF-A command to the FF-A library

  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

  Built QEMU SBSA with TPM enabled and Yielding implemented in the TPM Service

  Integration Instructions

  N/A
  

  
  

  ---

  
  

• [REBASE \& FF] Revert Mu Commit in Favor of edk2 Commit @os-d (#1533)
  
  Change Details

    ## Description

  This reverts the Mu SCSI Read Only Disk commit in favor of the edk2 commits.

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

  How This Was Tested

  N/A.

  Integration Instructions

  N/A.
  

  
  

  ---

  
  

• [CHERRY-PICK] MdeModulePkg: Add PcdDelayedDispatchMaxEntries @makubacki (#1534)
  
  Change Details

    ## Description

  The current fixed value of 8 for DELAYED_DISPATCH_MAX_ENTRIES is not large enough to accommodate platform usage. This change replaces the macro with a PCD that can be configured by platforms.

  In the case the default PCD value is too small, an error message explaining that the PCD should be updated will be printed followed by an assert.

  (cherry picked from commit 8a07311710acba244a1b44910324b3b4afd5889a)

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

  How This Was Tested

  • Tested on a a physical Intel platform that uses delayed dispatch

  Integration Instructions

  • Adjust gEfiMdeModulePkgTokenSpaceGuid.PcdDelayedDispatchMaxEntries as needed to accommodate the number of delayed dispatch entries used by a platform.
    

  
  

  ---

• CryptoPkg: Update shared crypto to v1.1.2 @apop5 (#1525)
  
  Change Details

    ## Description Update the shared crypto ext_dep to v1.1.2

  Full release notes are available at:
  https://github.com/microsoft/mu_crypto_release/releases/tag/v1.1.2

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

  How This Was Tested

  Booted Q35 and Sbsa with new version.

  Integration Instructions

  No integration necessary.
  

  
  

  ---

  
  

• feat: add scsi mode sense operation to detect write protection @mayank-microsoft (#1524)
  
  Change Details

    ## Description

  We encountered some errors where on attaching a ReadOnly disk led to write failures. We RCA'd the failure to the Volume protocol not being set to be write protected. We are proposing this change to update the blockIo protocol's media property to set Write protections based on performing a MODE SENSE operation.

  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

  We tested the change while booting a VM with VHD attached as read only mode and then without read-only mode. We don't encounter any errors which we were hitting earlier.

  Integration Instructions

  NA
  

  
  

  ---

  
  

• [CHERRY-PICK] Pick up FFA\_RUN solution from EDK2 @kuqin12 (#1529)
  
  Change Details

    ## Description

  BASECORE made a change for FFA_RUN change, but EDK2 already has a corresponding change.

  This change reverts the original fix and conform to EDK2 version.

  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 was tested on QEMU SBSA and booted to UEFI shell.

  Integration Instructions

  N/A
  

  
  

  ---

  
  

🐛 Bug Fixes

• Update FFA run interface to intake context as input argument @kuqin12 (#1526)
  
  Change Details

    ## Description

  The original implementation of ArmFfaLibRun does not return register values when invoked. However, FFA_RUN is normally some operations that requires retry, i.e. after FFA_YIELD or FFA_INTERRUPTED. Thus the context returned by FFA_RUN will be eaten if this is not returned.

  The change added an extra input argument to potentially return the output from monitor calls.

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

  How This Was Tested

  This is tested on QEMU SBSA and booted to UEFI shell.

  Integration Instructions

  One needs to pass in a pointer to context registers if the return values are needed.
  

  
  

  ---

  
  

Full Changelog: v2025020002.0.1...v2025020002.0.2