summaryrefslogtreecommitdiff
path: root/BaseTools/Source/Python
diff options
context:
space:
mode:
authorKun Qin <kuqin@microsoft.com>2025-04-04 16:54:38 -0700
committermergify[bot] <37929162+mergify[bot]@users.noreply.github.com>2025-06-19 06:17:18 +0000
commit73b0b5edaef19beb08b04869bc2e0f6328c9e604 (patch)
tree92622b167290903bea74656a40f7af070e1e9992 /BaseTools/Source/Python
parentc72d6384347bc57109d75fd56f2a5cdb8a40d132 (diff)
downloadedk2-73b0b5edaef19beb08b04869bc2e0f6328c9e604.zip
edk2-73b0b5edaef19beb08b04869bc2e0f6328c9e604.tar.gz
edk2-73b0b5edaef19beb08b04869bc2e0f6328c9e604.tar.bz2
StandaloneMmPkg: StandaloneMmIplPei: Use MM access to open the regions
Current MM IPL in PEI phase does not open the MMRAM regions through MM access PPI. This is causing some platforms like OVMF reading all `0xFF`s when trying to relocate the Standalone MM core. This change opens all the MMRAM regions provided by MM access PPI and closes + locks the regions after initial MM foundation setup, when MM Access PPI is available. Platforms that require MM access PPI can inject depex through libraries. Signed-off-by: Kun Qin <kun.qin@microsoft.com>
Diffstat (limited to 'BaseTools/Source/Python')
0 files changed, 0 insertions, 0 deletions