diff options
| author | Oliver Smith-Denny <osde@microsoft.com> | 2026-09-02 22:44:21 +0300 |
|---|---|---|
| committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2026-09-03 12:00:37 +0300 |
| commit | ee655c4d815231bd0916fbdde7a59f4dfdf0ee9f (patch) | |
| tree | ad942937e7bd7c905d0de18fefd5165db70a30c3 /BaseTools/Source/Python | |
| parent | 143032958ea9f97cfbab17a4fe7ada2e51c87d18 (diff) | |
| download | edk2-ee655c4d815231bd0916fbdde7a59f4dfdf0ee9f.tar.xz | |
MdeModulePkg: DxeIpl: Don't Duplicate Mem Alloc Hob for Stack
Currently, DxeIpl will allocate memory for the new DXE stack,
which creates a memory allocation HOB for that region. It will
then call UpdateStackHob() to find the stack HOB with the old
stack info and update the memory address/length to correspond
to the new stack. It then creates a new memory allocation HOB
for the old stack region as it needs to remain mapped.
This ends up creating two memory allocation HOBs for the new
stack: a regular memory allocation HOB for the AllocatePages()
call and then the stack HOB (which is a memory allocation HOB
with a special name).
When DXE Core ingests these, it will ignore one of the two HOBs
when it goes to allocate memory. However, this is incorrectly
describing handoff state. There never should be overlapping
memory allocation HOBs.
This commit updates DxeIpl behavior to instead find the old
stack HOB, convert it to a regular memory allocation HOB,
then find the memory allocation HOB for the new stack range
and convert it into the stack HOB.
Signed-off-by: Oliver Smith-Denny <osde@microsoft.com>
Diffstat (limited to 'BaseTools/Source/Python')
0 files changed, 0 insertions, 0 deletions
