MdeModulePkg: CoreDxe: Handle multilple MemoryAllocationModules

The current implementation from Dxe/Image/Image.c does not handle the
configuration where there might be multiple MemoryAllocationModules.

Given that the `ModuleName` is included in the hob data and used for
targetting the consumer, DXE core should specify the GUID when looking up
for its own MemoryAllocationModule.

This change adds a check to ensure the located hob is targetting DXE
core.

Signed-off-by: Kun Qin <[email protected]>

Author: kuqin12

MdeModulePkg/Core/Dxe/Image/Image.c

@@ -200,7 +200,9 @@ CoreInitializeImageServices (
       //
       // Find Dxe Core HOB
       //
-      break;
+      if (CompareGuid (&DxeCoreHob.MemoryAllocationModule->ModuleName, &gEfiCallerIdGuid)) {
+        break;
+      }
     }
 
     DxeCoreHob.Raw = GET_NEXT_HOB (DxeCoreHob);

MdeModulePkg/Core/Dxe/Mem/MemoryProfileRecord.c

@@ -549,7 +549,9 @@ RegisterDxeCore (
       //
       // Find Dxe Core HOB
       //
-      break;
+      if (CompareGuid (&DxeCoreHob.MemoryAllocationModule->ModuleName, &gEfiCallerIdGuid)) {
+        break;
+      }
     }
 
     DxeCoreHob.Raw = GET_NEXT_HOB (DxeCoreHob);