08 Jun 18:29

mu-automation

f7c042a

v2025110001.0.0 Latest

Latest

What's Changed

Migrate to R-EFI 6.0 @vineelko (#892)
Change Details
## Description
This PR consumed the major branch changes done in Patina as part of R-EFI 6.0 migration(release as version 22).
- Impacts functionality?
- Impacts security?
- Breaking change?
- Includes tests?
- Includes documentation?
How This Was Tested

cargo make all

Integration Instructions

Will merge this once OpenDevicePartnership/patina#1548 is merged and patina release 22 is made.

UefiHidDxeV2: Add keystroke repeat functionality @joschock (#883)
Change Details
## Description
Implement keyboard repeat for held keys, matching the behavior of the
legacy C HidKeyboardDxe driver:
- 500ms initial delay before repeat begins
- 20ms repeat rate (~50 keys/sec) while key is held
- Modifier keys, toggle keys, and non-spacing (dead) keys are excluded
- Last newly pressed repeatable key wins in multi-key reports
- Timer cancelled on key release or keyboard reset
- Impacts functionality?
- Impacts security?
- Breaking change?
- Includes tests?
- Includes documentation?
How This Was Tested

Included unit tests, tested on hardware at UEFI shell and confirmed expected repeat behavior.

Integration Instructions

None.

Fix missing UefiLib dependency in MfciPolicyParsingUnitTestApp @GiriMohanNaidu (#887)
Change Details
## Description
Added the missing UefiLib library class dependency to MfciPolicyParsingUnitTestApp.inf. The module uses UefiLib APIs but did not declare the dependency in its [LibraryClasses] section, causing build failures when the library was not implicitly pulled in by the platform DSC.
The module uses AsciiPrint() from UefiLib but did not declare the dependency in its LibraryClasses section.
- Impacts functionality? No — build fix only; no logic changes.
- Impacts security?
- Breaking change?
- Includes tests? N/A — fixes the test app itself so it builds correctly.
- Includes documentation?
How This Was Tested

Built MfciPkg/UnitTests/MfciPolicyParsingUnitTest/MfciPolicyParsingUnitTestApp.inf and confirmed the build completes without missing library errors.

Integration Instructions

N/A — consumers of MfciPkg do not need any changes; this only affects the unit test app build.
```
  </blockquote>
  <hr>
</details>
```

Migrate mu\_plus from mu\_uefi\_boot\_services crate to patina crate @vineelko (#881)
Change Details
## Description
- mu_uefi_boot_services is not maintained and its functionality is moved into patina.
- The mu_uefi_boot_services's crates.io point to non-existent repo.
- This cleanup is needed to move mu_plus's r-efi dependency to 6.0
Next, Once Patina is updated to r-efi 6.0 we can migrate mu_plus to patina vnext and r-efi to 6.0
- Impacts functionality?
- Impacts security?
- Breaking change?
- Includes tests?
- Includes documentation?
How This Was Tested

cargo make all worked. Will be tested in internal repos once r-efi 6.0 migration is done.

Integration Instructions

NA

AdvLoggerPkg/AdvancedLoggerLib: Print to HW if logger info is not available @makubacki (#876)

Change Details

## Description
In the course of testing advanced logger changes with edk2 Standalone MM on OVMF, there was a change needed in MmPlatformHobProducerLibOvmf in OvmfPkg to account for gAdvancedLoggerHobGuid in the HOBs that are passed to the MM environment.

Prior to this change, the system appeared to hang entering that environment:
INFO - Loading PEIM at 0x00005B95000 EntryPoint=0x00005B95340 StandaloneMmIplPei.efi
INFO - StandaloneMM IPL loading MM Core at MMRAM address 7FF0000
INFO - MmCoreImageBase  - 0x0000000007FF0000
INFO - MmCoreImageSize  - 0x0000000000010000
INFO - StandaloneMM IPL calling Standalone MM Core at MMRAM address - 0x0000000007FF1000
After the change, the issue is clearly printed to serial output: ("MmCore AdvancedLoggerGetLoggerInfo: Advanced Logger Hob not found")
INFO - Loading PEIM at 0x00005B94000 EntryPoint=0x00005B94340 StandaloneMmIplPei.efi
INFO - StandaloneMM IPL loading MM Core at MMRAM address 7FF0000
INFO - MmCoreImageBase  - 0x0000000007FF0000
INFO - MmCoreImageSize  - 0x0000000000010000
INFO - StandaloneMM IPL calling Standalone MM Core at MMRAM address - 0x0000000007FF1000
INFO - MmCore AdvancedLoggerGetLoggerInfo: Advanced Logger Hob not found
INFO - MmMain - 0x5B11000
INFO - MmramRangeCount - 0x4
INFO - MmramRanges[0]: 0x0000000006000000 - 0x1000
INFO - MmramRanges[1]: 0x0000000006001000 - 0xE000
INFO - MmramRanges[2]: 0x000000000600F000 - 0x1FE1000
INFO - MmramRanges[3]: 0x0000000007FF0000 - 0x10000
INFO - MmInitializeMemoryServices
INFO - MmAddMemoryRegion 2 : 0x000000000600F000 - 0x0000000001FE1000
INFO - HobSize - 0x538
INFO - MmHobStart - 0x7FEE810
INFO - MmInstallConfigurationTable For HobList
INFO - ASSERT [StandaloneMmCore] AdvancedLoggerLib.c(164): mLoggerInfo != ((void *) 0)
This change allows writes to proceed to hardware output if enabled even if the logger info is not available, to make information such as this available for debugging purposes.

Impacts functionality?

Impacts security?

Breaking change?

Includes tests?

Includes documentation?

How This Was Tested

Test MM entry with and without gAdvancedLoggerHobGuid in the HOB list.

Integration Instructions

N/A

⚠️ Breaking Changes

Delete HelloWorldRustDxe Component @vineelko (#882)
Change Details
## Description
HelloWorldRustDxe Component is currently being compiled for 32 bit causing PR gates to fail when dependent Rust packages do not compile(by design) for 32 bit. This PR deletes it completely.
- Impacts functionality?
- Impacts security?
- Breaking change?
- Includes tests?
- Includes documentation?
How This Was Tested

cargo make all

Integration Instructions

NA

🚀 Features & ✨ Enhancements

AdvancedLoggerPkg/MmCoreArm: Initialize LoggerInfo if not already set by earlier firmware phase @sureshkumarpMSFT (#886)
Change Details
## Description
In the MmCoreArm instance of AdvancedLoggerLib, AdvancedLoggerGetLoggerInfo() previously assumed that an earlier firmware phase (e.g. BL31 prior to StandaloneMM) had already initialized the ADVANCED_LOGGER_INFO header at PcdAdvancedLoggerBase. On ARM boot flows where StandaloneMM is the first phase to touch this buffer, the signature check in subsequent logger calls fails and no log records are written.

This change adds a one-time, in-place initialization of the ADVANCED_LOGGER_INFO header inside AdvancedLoggerGetLoggerInfo() when the signature is not already valid:
- Impacts functionality?
- Impacts security?
- Breaking change?
- Includes tests?
- Includes documentation?
How This Was Tested

Verified on an ARM platform where no pre-StandaloneMM entity initializes the AdvancedLogger buffer

Integration Instructions

N/A

🐛 Bug Fixes

Fix SWM init retry when SRE is not ready @mikitl (#888)
Change Details
## Description
GopRegisteredCallback sets mGop when it finds GOP but exits early if SRE is not available yet. Because mGop remains set, the callback never retries on subsequent GOP notifications, so SWM never initializes.

Reset mGop to NULL when SRE is not found so the callback can retry.
- Impacts functionality?
- Impacts security?
- Breaking change?
- Includes tests?
- Includes documentation?
How This Was Tested

Tested on:
- ARM64 platform with GPU driver that installs GOP during early display enumeration, before GopOverrideDxe and SRE have processed it
- Verified SWM callback retries and completes Stage2 initialization after SRE becomes available
- Confirmed Front Page and on-screen keyboard render correctly
- Verified no regression when GOP and SRE appear simultaneously (standard boot path)
Integration Instructions

N...

Contributors

mikitl, makubacki, and 4 other contributors

Assets 2

02 Apr 14:55

mu-automation

v2025110000.0.3

31f2b85

v2025110000.0.3

What's Changed

[REBASE \& FF] Copy FltUsedLib to MsCorePkg @os-d (#864)
Change Details
## Description
FltUsedLib is a library that has a single line, adding a reference to _fltused, which is needed by MSVC and clang when building floating point code.

FltUsedLib is only used in mu_plus, so in order to reduce deltas from edk2, it is moved to mu_plus. This commit then updates references in mu_plus to this new library.

A PR will be put up to mu_basecore to drop the library after this merges.
- Impacts functionality?
- Impacts security?
- Breaking change?
- Includes tests?
- Includes documentation?
How This Was Tested

Build testing.

Integration Instructions

Platforms should update to FltUsedLib|MsCorePkg/Library/FltUsedLib/FltUsedLib.inf in their DSCs. This change is not a breaking change, but the removal in mu_basecore will be.
```
  </blockquote>
  <hr>
</details>
```

Global: Remove backport workflow. @apop5 (#859)
Change Details
Description

The switch from dev/release to just relase left the backport workflow in the repo. Though it will
not be triggered, dependabot will continue
to attempt to update the github actions used.

Remove the workflow to reduce unused workflows and to prevent dependabot from attempting to update.
- Impacts functionality?
- Impacts security?
- Breaking change?
- Includes tests?
- Includes documentation?
How This Was Tested

N/A

Integration Instructions

N/A

Full Changelog: v2025110000.0.2...v2025110000.0.3

Contributors

os-d and apop5

Assets 2

23 Mar 20:12

mu-automation

v2025110000.0.2

f5b19d4

v2025110000.0.2

What's Changed

UefiTestingPkg: MpManagement clangpdb compatibility @apop5 (#858)
Change Details
Description

Make the MpManagement FunctionalTest compile with clangpdb.

Correct some uninitialized variable paths, and use macros for
loading variables it registers in assembly.
- Impacts functionality?
- Impacts security?
- Breaking change?
- Includes tests?
- Includes documentation?
How This Was Tested

ClangPdb Build.

Integration Instructions

No integration necessary.

Full Changelog: v2025110000.0.1...v2025110000.0.2

Contributors

apop5

Assets 2

18 Mar 21:19

mu-automation

v2025110000.0.1

c79571d

v2025110000.0.1

What's Changed

UefiTestingPkg: FlatPageTableLib: Include Public Page Table Defs @os-d (#857)
Change Details
## Description
In mu_basecore commit 5ba3221588832c47249a6db1f38b490f034e07ca the X86 Page Table definitions were moved from CpuPageTableLib to MdePkg. Consume these from the new location and define a macro that remained in the private header in edk2.
- Impacts functionality?
- Impacts security?
- Breaking change?
- Includes tests?
- Includes documentation?
How This Was Tested

Built.

Integration Instructions

N/A.
```
  </blockquote>
  <hr>
</details>
```

Replace memcpy with CopyGuid. @jaykrell (#852)

Change Details

There is a link error here, due to struct assignment being memcpy with some compilers.
Replace struct assignment with CopyGuid.

Full Changelog: v2025110000.0.0...v2025110000.0.1

Contributors

jaykrell and os-d

Assets 2

11 Mar 04:11

apop5

v2025110000.0.0

92e607e

v2025110000.0.0

First release compatible with mu_basecore release/202511

Please view Readme.rst for release information.

Assets 2

10 Feb 19:22

mu-automation

v2025020003.0.2

3afa423

v2025020003.0.2

What's Changed

AdvLoggerPkg: Initialize structures in LineParserTestApp @makubacki (#828)
Change Details
## Description
Logger info structures are not zeroed and initialized right now, causing garbage data to be read in some fields and impact test results.
- Impacts functionality?
- Impacts security?
- Breaking change?
- Includes tests?
- Includes documentation?
How This Was Tested
- Run LineParserTestApp on QEMU Q35
Integration Instructions
- N/A

Full Changelog: v2025020003.0.1...v2025020003.0.2

Contributors

makubacki

Assets 2

10 Feb 05:10

mu-automation

v2025020003.0.1

3496fc1

v2025020003.0.1

What's Changed

[REBASE \& FF] Fix Memory Tests to Run on Patina @os-d (#825)
Change Details
## Description
See individual commit descriptions for full details. This changeset updates the paging audit simple test, full audit, and memory protections test app to run on Patina.
- Impacts functionality?
- Impacts security?
- Breaking change?
- Includes tests?
- Includes documentation?
How This Was Tested

Tested on physical Intel, Q35, and SBSA.

Integration Instructions

Ensure the platform is producing the memory protection HOB with:
```
DxeSettings.HeapGuardPolicy.Fields.UefiPageGuard = 0;
DxeSettings.HeapGuardPolicy.Fields.UefiPoolGuard = 0;
```
Until Patina enables those features, otherwise those tests will execute and will fail due to no guard pages enabled.

This is a breaking change because it depends on mu_basecore version >= v2025020003.0.2 as some header definitions are depended on in that release.

Update Adv Logger Info to V6 [Rebase \& FF] @makubacki (#826)
Change Details
## Description
AdvLoggerPkg: Define a single advanced logger info version

Currrently, ADVANCED_LOGGER_INFO_VER is being used to set and check
the version field in the ADVANCED_LOGGER_INFO struct.

This more clearly defines that version to be associated with the
log info structure and breaks out the Hardware Level version to a
macro (ADVANCED_LOGGER_INFO_HW_LVL_SUPPORTED_VER) that clearly shows
that is an identifier for hardware level support being present in
the logger info version.

AdvLoggerPkg: Bump ADVANCED_LOGGER_INFO_VER to 6

Updates the major version to 6 to account for the NewLoggerInfoAddress
field that was added to ADVANCED_LOGGER_INFO.
- Impacts functionality?
- Impacts security?
- Breaking change?
- Includes tests?
- Includes documentation?
How This Was Tested
- AdvLoggerPkg CI build
- AdvLoggerPkg QEMU Q35 boot to EFI shell and dump log with EFI app
- Intel physical platform boot to OS and decode log (in progress)
- Arm platform test (todo)
Integration Instructions
- Ensure all adv logger code is updated to the same version and you're using the latest version of the applications in AdvLoggerPkg.

AdvLoggerPkg: DecodeUefiLog handle frequency errors. @apop5 (#824)
Change Details
## Description
When calling DecodeUefiLog, if the system was not able to provide a frequency in the log, it will be reported as 0. With no verification check of a zero frequency, DecodeUefiLog would attempt a divide by zero when converting time to nano seconds.

Add a check that prevents divide by zero. This will report times of 0 for all timestamps in the decoded log.
- Impacts functionality?
- Impacts security?
- Breaking change?
- Includes tests?
- Includes documentation?
How This Was Tested

On a physical platform where no timer frequency was reported, encountered a python exception.
After change, log was correctly retrieved and displays a timestamp of 0.

Integration Instructions

No integration necessary.

Refactor HID Keyboard Reset support @joschock (#823)
Change Details
## Description
This PR changes how CTRL-ALT-DEL resets are handled by the HID stack. Previously, they were handled by the lower layer key processing code; but this caused them to be handled at an implementation-defined TPL based on what TPL the input reports are generated at by the HID I/O layer.

This change moves the CTRL-ALT-DEL to use the existing SimpleTextInEx key registration infrastructure to handle the reset logic, effectively moving the reset handling up to a higher level of abstraction.

This also simplifies disabling this capability behind a feature flag should it be desirable in the future to separate reset logic from the HID stack entirely.
- Impacts functionality?
- Impacts security?
- Breaking change?
- Includes tests?
- Includes documentation?
How This Was Tested

Verified CTRL-ALT-DEL resets system from UEFI shell and that reset occurs at TPL_CALLBACK.

Integration Instructions

N/A

Configure watchdog interrupt for ARM platform @rohansenUSA (#820)
Change Details
## Description
When using MpManagement to suspend all cores to a C-state that powers down the core the non-secure watchdog is being used to wake up a core after a certain amount of time.

On ARM reference platforms the non-secure watchdog interrupt is a level interrupt and active high. and this PR configures the interrupt trigger accordingly. Also, when all cores are powered down interrupt IRM (Interrupt Routing Mode) can't be used and the interrupt have to be routed to a specific core using the affinity fields. This PR programs the interrupt to go to the BSP.
- Impacts functionality?
- Impacts security?
- Breaking change?
- Includes tests?
- Includes documentation?
How This Was Tested

Tested on custom Microsoft hardware.

Following use case was run:
1. Program watchdog timer.
2. Power down cores.
3. Watchdog interrupt to wake up BSP.
Integration Instructions

N/A
```
  </blockquote>
  <hr>
</details>
```

MsWheaPkg: Change debug prints to avoid confusion @kuqin12 (#819)
Change Details
## Description
The current debug output labels all HwErrRec entries as error records. While technically accurate given the “Hardware Error Record” naming, this can be misleading, as some entries are informational rather than actual errors.

This change updates the debug output to use “telemetry record” instead, reducing the risk of confusion.
- Impacts functionality?
- Impacts security?
- Breaking change?
- Includes tests?
- Includes documentation?
How This Was Tested

Debug print change only, non-functional.

Integration Instructions

N/A

Rendering Engine Fixes [Rebase \& FF] @makubacki (#818)
Change Details
## Description
MsGraphicsPkg/RenderingEngineDxe: Defensive checks for global GOP pointer

Verify mParentGop is valid before use.

MsGraphicsPkg/RenderingEngineDxe: Defensive checks for global GOP pointer

Verify mParentGop is valid before use.
- Impacts functionality?
- Impacts security?
- Breaking change?
- Includes tests?
- Includes documentation?
How This Was Tested
- CI, build and verify GOP start and operation in QEMU Q35, and "disconnect -r" succeeds
Integration Instructions
- N/A

Revise OSK error messages @joschock (#817)
Change Details
## Description
Present OSK messages include the error level (e.g. "[ERROR] OSK: ").

This PR removes those tags. This allows better filtering of logs for actual actionable errors, as well as avoiding redundancy when interpreted by a log viewer that also tags each message according to the error level.

Debug message changes only, no functional change.
- Impacts functionality?
- Impacts security?
- Breaking change?
- Includes tests?
- Includes documentation?
How This Was Tested

Booted system, observed error messages changed as expected.

Integration Instructions

N/A

AdvLoggerPkg: Fix memory bucket stability @makubacki (#799)

Change Details

## Description
Right now, the PEI Core instance of AdvancedLoggerLib will always allocate the logger buffer as EfiRuntimeServicesData. This means it is not allocated into the DXE Core managed RT Services Data memory bucket. The DXE Core instance of AdvancedLoggerLib either continues to use this buffer it is provided or allocates a new EfiReservedMemoryType buffer.

This change always allocates a EfiReservedMemoryType buffer in the DXE Core instance to ensure it is allocated from the reserved memory type buckets setup by the DXE Core. The PEI Core logger buffer is updated to be EfiBootServicesData so it does not affect...

Contributors

eeshanl, makubacki, and 9 other contributors

Assets 2

19 Sep 19:03

mu-automation

v2025020003.0.0

ec779d3

v2025020002.0.2

What's Changed

Dev branch tear down [Rebase & FF] by @apop5 in #753
Remove unused Rust dependencies @makubackiin #754

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

Contributors

apop5

Assets 2

Releases: microsoft/mu_plus

v2025110001.0.0

What's Changed

How This Was Tested

Integration Instructions

How This Was Tested

Integration Instructions

How This Was Tested

Integration Instructions

How This Was Tested

Integration Instructions

How This Was Tested

Integration Instructions

⚠️ Breaking Changes

How This Was Tested

Integration Instructions

🚀 Features & ✨ Enhancements

How This Was Tested

Integration Instructions

🐛 Bug Fixes

How This Was Tested

Integration Instructions

Contributors

Uh oh!

v2025110000.0.4

What's Changed

How This Was Tested

Integration Instructions

How This Was Tested

Integration Instructions

How This Was Tested

Integration Instructions

Notes

How This Was Tested

Integration Instructions

Contributors

Uh oh!

v2025110000.0.3

What's Changed

How This Was Tested

Integration Instructions

Description

How This Was Tested

Integration Instructions

Contributors

Uh oh!

v2025110000.0.2

What's Changed

Description

How This Was Tested

Integration Instructions

Contributors

Uh oh!

v2025110000.0.1

What's Changed

How This Was Tested

Integration Instructions

Contributors

Uh oh!

v2025110000.0.0

Uh oh!

v2025020003.0.3

What's Changed

How This Was Tested

Integration Instructions

🐛 Bug Fixes

How This Was Tested

Integration Instructions

Contributors

Uh oh!

v2025020003.0.2

What's Changed

How This Was Tested

Integration Instructions

Contributors

Uh oh!

v2025020003.0.1

What's Changed

How This Was Tested

Integration Instructions