Re: DxeIpl module cannot find DXE entry point

[Laszlo Ersek <lersek@redhat.com>]

On 08/15/18 02:38, Zeng, Star wrote:
> You may try report the FVMAIN_COMPACT with the way like below. Then PeiCore's FvInfo notification will decompress the FVMAIN_COMPACT and build FV HOB for decompressed FVMAIN for DXE phase. FvInfo is the standard way, FvHob is produce for DXE phase. PeiCore only processes FvHob when PcdFrameworkCompatibilitySupport = TRUE.
> 
>   //
>   // Let PEI know about the DXE FV so it can find the DXE Core
>   //
>   PeiServicesInstallFvInfoPpi (
>     NULL,
>     (VOID *)(UINTN) PcdGet32 (PcdOvmfDxeMemFvBase),
>     PcdGet32 (PcdOvmfDxeMemFvSize),
>     NULL,
>     NULL
>     );

Ah, right! I should have looked at the comments in PeiFvInitialization()
[OvmfPkg/PlatformPei/Fv.c], from Jordan's commit b36f701d4f925.

The function calls both BuildFvHob() and PeiServicesInstallFvInfoPpi(),
and the comments on them explain the different purposes. One is for the
DXE Core to dispatch drivers from, the other is for the PEI Core to find
the DXE Core in.

Thanks!
Laszlo