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

v2025020002.0.1

What's Changed

• [FF-A] Update Header to Include FFA\_NS\_RES\_INFO\_GET @Raymond-MS (#1520)
  
  Change Details

    ## Description

  Add FFA_NS_RES_INFO_GET to the ARM FF-A header.

  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

  Verified through QemuSbsa build and FfaPartitionTestApp.

  Integration Instructions

  N/A

    </blockquote>
    <hr>
  </details>
  

• [CHERRY-PICK] workflow: Update BaseTool extdep weekly @Javagedes (#1516)
  
  Change Details

    ## Description

  Creates a new recurring workflow that runs weekly. This workflow finds all releases that occurred in the last 7 days, and finds the most recent release for each associated branch (e.g. if three releases happened [v202502000.0.1, dev-v202502000.0.1, v202502000.0.2], we reduce that to only [v202502000.0.2', 'dev-v202502000.0.1'] because two of them target the same release/202502 branch).

  If we do not find any releases, we abort early. Otherwise for each release, we will create a PR for the specific branch, updating the base tools extdep to the most recent release. If a PR already exists for an older version, we will close it.

  Cherry-pick of #1383

  An additional commit after this cherry-pick is applied to remove the dev branch logic.

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

  How This Was Tested

  N/A

  Integration Instructions

  N/A

    </blockquote>
    <hr>
  </details>
  

• [Cherry-Pick] NetworkPkg/UefiPxeBcDxe: Add buffer check before reporting status code @apop5 (#1517)
  
  Change Details

    ## Description

  When PxeBcLoadBootFile() fails, it reports a status code to notify listeners (such as telemetry/SEL logging drivers) about the error. However, the current implementation reports the status code for all error conditions, including benign cases, such as where the caller passes Buffer == NULL with EFI_BUFFER_TOO_SMALL to query the required size.

  This causes false positive error reports in telemetry systems, as EFI_BUFFER_TOO_SMALL with Buffer == NULL is an expected and normal operation for size queries, not an actual error condition.

  The PXE-E05 error message is already correctly guarded with the condition "(Status == EFI_BUFFER_TOO_SMALL) && (Buffer != NULL)", but the status code reporting was unconditional.

  Add a buffer null check before REPORT_STATUS_CODE_WITH_EXTENDED_DATA to ensure status codes are only reported for actual errors:

  • Report when Status != EFI_BUFFER_TOO_SMALL (all other errors)
  • Report when Status == EFI_BUFFER_TOO_SMALL AND Buffer != NULL (PXE-E05)
  • Skip when Status == EFI_BUFFER_TOO_SMALL AND Buffer == NULL (size query)

  This prevents spurious error logs while maintaining proper error reporting for genuine failures including PXE-E05, PXE-E07, PXE-E09, PXE-E99, and all other error conditions.

  (cherry picked from commit d3a64baf4b6706367c30a4886c01e95589861c9f)

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

  How This Was Tested

  PXE booting physical platform. After change, no longer encounter double status code listener error report.

  Integration Instructions

  No integration necessary.
  

  
  

  ---

  
  

• MockPolicyLibCommon : Add SetPolicy @Irene-IY (#1512)
  
  Change Details

    ## Description

  Add SetPolicy into MockPolicyLibCommon

  Signed-off-by : Irene-IY ireneyang@ami.com

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

  How This Was Tested

  CI test

  Integration Instructions

  N/A
  

  
  

  ---

  
  

• [CHERRY-PICK] MdePkg: Add MockSpiNorFlashProtocol @PaddyDengAmi (#1507)
  
  Change Details

    ## Description

  Add MockSpiNorFlashProtocol for google test components to use.

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

  How This Was Tested

  Consumed by other google test

  Integration Instructions

  N/A
  

  
  

  ---

  
  

• [REBASE \& FF] Prevent AP GP Fault @os-d (#1515)
  
  Change Details

    ## Description

  This PR reverts a MU CHANGE to prevent the AP deadlock with a spinlock. This was later determined to not be necessary and instead separate a GDT/TSS is used for each AP, in addition to forcing a graceful transition to those.

  This PR also reverts and reapplies a MU_CHANGE as part of that MU_CHANGE was moved to the above new commit and will be upstreamed to edk2 separately. In addition, another piece of this memory protections MU_CHANGE was already changed in 2e259b7, so that is also dropped.

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

  How This Was Tested

  Tested on physical Intel client and server platforms that were experiencing the AP deadlock.

  Integration Instructions

  N/A.

    </blockquote>
    <hr>
  </details>
  

Full Changelog: v2025020002.0.0...v2025020002.0.1

v2025020002.0.0

What's Changed

• [Backport] [Release/202502] Backport/support/pkcs7 encrypt by @Flickdm in #1489
• Dev branch tear down [Rebase & FF] by @apop5 in #1505

Full Changelog: v2025020001.0.6...v2025020002.0.0

v2025020001.0.6

What's Changed

• Repo File Sync: Update actions/checkout to v5 by @mu-automation[bot] in #1478
• • [release/202502] Update BaseTools ext dep to v2025020001.0.5 by @mu-automation[bot] in #1480
• Remove unnecessary cargo files by @magravel in #1482
• UefiCpuPkg: X64 MpLib: Spinlock RestoreVolatileRegisters by @os-d in #1487

Full Changelog: v2025020001.0.5...v2025020001.0.6

dev-v2025020001.0.6

What's Changed

• Repo File Sync: Update actions/checkout to v5 by @mu-automation[bot] in #1478
• Remove unnecessary cargo files by @magravel in #1482
• Support/Pkcs7Encrypt by @Flickdm in #1484
• Repo File Sync: Update to Mu DevOps v16.0.0 by @mu-automation[bot] in #1485
• Update Crypto Driver by @Flickdm in #1488
• UefiCpuPkg: X64 MpLib: Spinlock RestoreVolatileRegisters by @os-d in #1487

New Contributors

• @magravel made their first contribution in #1482

Full Changelog: dev-v2025020001.05...dev-v2025020001.0.6

dev-v2025020001.05

What's Changed

• BaseTools: Fix extdep for base tool binaries by @apop5 in #1476

Full Changelog: dev-v2025020001.0.4...dev-v2025020001.05

release-v2025020001.0.5

What's Changed

• BaseTools: Fix extdep for base tool binaries by @apop5 in #1477

Full Changelog: v2025020001.0.4...v2025020001.0.5

release-v2025020001.0.4

Release for generating a new basetools ext_dep.

What's Changed

• [release/202502] Update BaseTools ext dep to v2025020001.0.3 by @mu-automation[bot] in #1466

Full Changelog: v2025020001.0.3...v2025020001.0.4

dev-v2025020001.0.4

releasing to generating a new basetools ext_dep.

What's Changed

• [dev/202502] Update BaseTools ext dep to dev-v2025020001.0.3 by @mu-automation[bot] in #1467
• Revert "[dev/202502] Update BaseTools ext dep to dev-v2025020001.0.3 (#1467)" by @apop5 in #1471
• [202502] pip-requirements.txt: Update edk2-pytools to latest by @Javagedes in #1468
• [CHERRY-PICK] [REBASE & FF] MdeModulePkg: XhciDxe: Fix USB reset issue by @berlin-with0ut-return in #1473
• Add the functions from LocalApicLib.h to MockLocalApicLib. by @ElvisYangGit in #1444
• build_rule.template: Update version to 3.00 by @makubacki in #1475

Full Changelog: dev-v2025020001.0.3...dev-v2025020001.0.4

release-v2025020001.0.3

What's Changed

• build\_rule.template: Update version to 3.00 @makubacki (#1475)
  
  Change Details

    ## Description

  Right now, the 2502 build_rule.template version is 2.04 while the 2405 file version is 2.24. This causes users to not be informed that the file is different in their local workspace when they move to 2502 causing the build to use the incorrect (2405) build_rule file. This updates the version to 3.00. Even if, 2405 continues to update the version (e.g. 2.25), 2502 can update in the 3.xx series independently and always be considered greater so when a user does transition they will be notified to update their Conf dir.

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

  How This Was Tested

  • Local build

  Integration Instructions

  • N/A - Users will now be informed they need to delete/update their local Conf directory
    

  
  

  ---

• Add the functions from LocalApicLib.h to MockLocalApicLib. @ElvisYangGit (#1444)
  
  Change Details

    ## Description

  Add mock function "GetInitialApicId" for unit testing.
  EDK2 PR: tianocore/edk2#11330

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

  How This Was Tested

  The mock library API can be consumed successfully in unit test.

  Integration Instructions

  N/A
  

  
  

  ---

  
  

• [CHERRY-PICK] [REBASE \& FF] MdeModulePkg: XhciDxe: Fix USB reset issue @berlin-with0ut-return (#1473)
  
  Change Details

    ## Description

  Cherry-picks a fix from edk2 to fix USB reset issue seen on Intel platforms.
  Original PR: tianocore/edk2#11382

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

  How This Was Tested

  Booted to frontpage on Intel device and observed the page fault no longer occurs when unplugging USB externals.

  Integration Instructions

  N/A
  

  
  

  ---

  
  

• [202502] pip-requirements.txt: Update edk2-pytools to latest @Javagedes (#1468)
  
  Change Details

    ## Description

  This commit updates to the most recent version of the edk2-pytools to ensure they stay up to date.

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

  How This Was Tested

  N/A

  Integration Instructions

  N/A
  

  
  

  ---