Tianocore/edk2.git/MdeModulePkg, branch dependabot/github_actions/actions/create-github-app-token-3

MdeModulePkg: Added several mock libraries for google test

2026-04-02T03:27:19+00:00

Added several mock libraries for google test so one can make google test drives consuming those libraries: - MockTpmMeasurementLib - MockFirmwareVolumeShadowPpi Signed-off-by: Paddy Deng

MdeModulePkg: VariableSmmRuntimeDxe: Fix MM communicate v3 buffer sizing

2026-03-25T17:47:59+00:00

This change updates `VariableSmmRuntimeDxe` to correctly size its runtime communication buffer when `EFI_MM_COMMUNICATION3_PROTOCOL` is present. In the current flow, the runtime variable path may use MM communication v3, but the input size is first validated against the global variable `mVariableBufferPayloadSize`. The size is then validated a second time during communication buffer initialization using the v3 header size, which results in `GetVariable` calls with sufficiently large buffers consistently failing. This update makes the allocation logic v3‑aware so that the runtime variable communication buffer matches the header format actually in use, avoiding failures for larger variable transactions. Signed-off-by: Kun Qin

Revert "MdeModulePkg/PciBusDxe: Degrade MEM64 to PMEM64..."

2026-03-24T02:11:23+00:00

This reverts commit f6489621b8ae1164c5e4930902988ba7c86847ba. MdeModulePkg/PciBusDxe: Degrade MEM64 to PMEM64 when bridge lacks MEM64 A number of compatibility issues have been reported with this change to the PciBusDxe behavior. Revert this change at this time to give time for all the issues to be reviewed and options for supporting this new behavior to be evaluated and fully validated. Signed-off-by: Michael D Kinney

MdeModulePkg/Core: Validate DXE event signature before usage

2026-03-23T18:43:11+00:00

fixes: #11112 Currently, function RegisterProtocolNotify() doesn't check the validity of event and it accepts any event pointer as long as pointer isn't NULL. However event could be closed and freed which could lead to use after free. Always check event signature before usage and return EFI_INVALID_PARAMTER for events with invalid signature. Signed-off-by: Khalid Ali

MdeModulePkg/SpiNorFlashJedecSfdp: Limit debug output

2026-03-23T16:30:18+00:00

Change debug print level from DEBUG_INFO to DEBUG_VERBOSE to limit excessive output. Since Spinor Sfdp operations can generate a large number of debug messages due to frequent read/write/erase actions, this change reduces log verbosity at the INFO level. Signed-off-by: Abdul Lateef Attar

MdeModulePkg: : revert EndofDxeEvent TPLs to TPL_NOTIFY for FPDT

2026-03-19T03:39:15+00:00

commit aa02571 ("MdeModulePkg: Change EndofDxeEvent TPLs to TPL_CALLBACK") changed EndOfDxeEvent TPLs from TPL_NOFIY to TPL_CALLBACK. However this commit makes a boot failure on the FVP platform when FPDT ACPI table generation is enabled: [FirmwarePerformanceDxe] Error when lock variable FirmwarePerformance, Status = Write Protected ASSERT_EFI_ERROR (Status = Write Protected) ASSERT [FirmwarePerformanceDxe] FirmwarePerformanceDxe.c(405): !(((RETURN_STATUS)(Status)) >= 0x8000000000000000ULL) Currently, EVT_NOTIFY_SIGNAL events are managed in FILO order, as new events are inserted using InsertHeadList(). The sequence is as follows: 1. DxeCore initializes DxeCorePerformanceLib, whose constructor creates an EndOfDxe event (gEfiEndOfDxeEventGroupGuid) with the ReportFpdtRecordBuffer() callback. 2. MmCommunicationDxe (in ArmPkg) creates another EndOfDxe event to notify StandaloneMm. This event is inserted ahead of the one created in (1). 3. PlatformBootManagerBeforeConsole() signals EndOfDxe, which triggers the event created in (2) first. 4. When the callback from (2) runs, StandaloneMm calls LockVariablePolicy(). 5. The callback from (1) is then invoked and attempts to update FPDT via InstallFirmwarePerformanceDataTable(). During this process, it tries to register a variable policy for the FirmwarePerformance variable. However, since the Variable Policy interface was locked in (4), the operation fails with EFI_WRITE_PROTECTED. To resolve this issue, revert EndofDxeEvent TPLs to TPL_NOTIFY for FPDT. Fixes: aa02571 ("MdeModulePkg: Change EndofDxeEvent TPLs to TPL_CALLBACK") Signed-off-by: Yeoreum Yun

MdeModulePkg/PeiCore: Accept MemoryDiscoveredPpi from SecCore

2026-03-19T02:02:47+00:00

PeiCore assumes that it runs initially from the temporary memory and switches to physical memory after PS::InstallPeiMemory() reports the physical memory range for PEI. This change enables PeiCore to run initially from the physical memory when MemoryDiscoveredPpi is passed from SEC. Signed-off-by: Ray Ni

MdeModulePkg: Change EndofDxeEvent TPLs to TPL_CALLBACK

2026-03-17T02:38:07+00:00

Change FPDT events at EndOfDxe to TPL_CALLBACK as TPL_NOTIFY is not necessary. Signed-off-by: Sherry Fan

MdeModulePkg: Update performance measurements to use new perf macros

2026-03-17T02:38:07+00:00

Updates BmBoot and dispatcher to use new perf macros. Signed-off-by: Sherry Fan

MdeModulePkg/PciBusDxe: Add optional CRS retry for enumeration

2026-03-17T02:03:32+00:00

The current PciDevicePresent() implementation skips PCIe devices that return Configuration Request Retry Status (CRS) during enumeration. This causes devices that are slow to initialize (e.g., after power-on or reset) to be missed entirely. Per PCIe Base Specification Rev 3.1 Section 2.3.1, when CRS Software Visibility is enabled and a device returns CRS, the Root Complex reports Vendor ID as 0x0001. The specification recommends software retry the configuration read until the device becomes ready. This patch adds optional CRS retry support controlled by PCDs: - PcdPciCrsRetryIntervalUs: Retry interval in microseconds (default 10000) - PcdPciCrsTimeoutSeconds: Total timeout in seconds (default 0) By default (PcdPciCrsTimeoutSeconds=0), CRS retry is disabled and devices returning CRS are skipped during enumeration. Platforms requiring CRS retry support should set PcdPciCrsTimeoutSeconds to a non-zero value. Additional improvements: - Add PCI_VENDOR_ID_NONE and PCI_VENDOR_ID_CRS macros for readability - Handle invalid PCD configurations (e.g., zero retry interval) - Add DEBUG output for CRS detection, successful retry, and timeout Signed-off-by: Ashish Singhal