The entry point of PE/COFF Image for the DXE Core. \r
\r
This function is the entry point for the DXE Core. This function is required\r
- to call ProcessModuleEntryPointList() and ProcessModuleEntryPoint() is never\r
+ to call ProcessModuleEntryPointList() and ProcessModuleEntryPointList() is never\r
expected to return. The DXE Core is responsible for calling ProcessLibraryConstructorList()\r
as soon as the EFI System Table and the image handle for the DXE Core itself have\r
been established.\r
these SEC-hosted PPIs to its PPI database such that both the PEI\r
Foundation and any modules can leverage the associated service calls\r
and/or code in these early PPIs. \r
- @param OldCoreData Pointer to Original startup information.\r
+ @param Context A pointer to a private context structure defined by the PEI Core\r
+ implementation. The implementation of _ModuleEntryPoint() must set\r
+ this parameter is NULL to indicate that this is the first PEI phase.\r
\r
**/\r
VOID\r
ProcessModuleEntryPointList (\r
IN CONST EFI_SEC_PEI_HAND_OFF *SecCoreData,\r
IN CONST EFI_PEI_PPI_DESCRIPTOR *PpiList,\r
- IN VOID *OldCoreData\r
+ IN VOID *Context\r
);\r
\r
#endif\r
Autogenerated function that calls the library constructors for all of the module's\r
dependent libraries.\r
\r
- This function must be called by the PEI Core once an initial PEI Services Table has been established.\r
+ This function must be called by _ModuleEntryPoint().\r
This function calls the set of library constructors for the set of library instances that a\r
- module depends on. This include library instances that a module depends on directly and library\r
+ module depends on. This includes library instances that a module depends on directly and library\r
instances that a module depends on indirectly through other libraries. \r
This function is autogenerated by build tools and those build tools are responsible for collecting\r
the set of library instances, determine which ones have constructors, and calling the library\r
Autogenerated function that calls the library descructors for all of the module's\r
dependent libraries.\r
\r
- This function may be called by _ModuleEntryPoint()or ExitDriver().\r
+ This function may be called by _ModuleEntryPoint()or Exit().\r
This function calls the set of library destructors for the set of library instances\r
that a module depends on. This includes library instances that a module depends on\r
directly and library instances that a module depends on indirectly through other libraries. \r
The entry point of PE/COFF Image for the DXE Core. \r
\r
This function is the entry point for the DXE Core. This function is required\r
- to call ProcessModuleEntryPointList() and ProcessModuleEntryPoint() is never\r
+ to call ProcessModuleEntryPointList() and ProcessModuleEntryPointList() is never\r
expected to return. The DXE Core is responsible for calling ProcessLibraryConstructorList()\r
as soon as the EFI System Table and the image handle for the DXE Core itself have\r
been established.\r