PEI Dispatcher Dependency Evaluator\r
\r
This routine evaluates a dependency expression (DEPENDENCY_EXPRESSION) to determine\r
- if a driver can be scheduled for execution. The criteria for\r
- schedulability is that the dependency expression is satisfied.\r
+ if a driver can be scheduled for execution. The criteria to be scheduled is\r
+ that the dependency expression is satisfied.\r
\r
Copyright (c) 2006 - 2019, Intel Corporation. All rights reserved.<BR>\r
SPDX-License-Identifier: BSD-2-Clause-Patent\r
}\r
\r
/**\r
- This routine enable a PEIM to register itself to shadow when PEI Foundation\r
- discovery permanent memory.\r
+ This routine enables a PEIM to register itself for shadow when the PEI Foundation\r
+ discovers permanent memory.\r
\r
@param FileHandle File handle of a PEIM.\r
\r
}\r
\r
//\r
- // Locate the corresponding FV_PPI according to founded FV's format GUID\r
+ // Locate the corresponding FV_PPI according to the format GUID of the FV found\r
//\r
Status = PeiServicesLocatePpi (\r
&FvInfo2Ppi.FvFormat,\r
);\r
\r
//\r
- // Inform the extracted FvImage to FV HOB consumer phase, i.e. DXE phase\r
+ // Expose the extracted FvImage to the FV HOB consumer phase, i.e. DXE phase\r
//\r
BuildFvHob (\r
(EFI_PHYSICAL_ADDRESS) (UINTN) FvHeader,\r
}\r
\r
/**\r
- Get instance of PEI_CORE_FV_HANDLE for next volume according to given index.\r
+ Gets a PEI_CORE_FV_HANDLE instance for the next volume according to the given index.\r
\r
- This routine also will install FvInfo PPI for FV HOB in PI ways.\r
+ This routine also will install an instance of the FvInfo PPI for the FV HOB\r
+ as defined in the PI specification.\r
\r
@param Private Pointer of PEI_CORE_INSTANCE\r
- @param Instance The index of FV want to be searched.\r
+ @param Instance Index of the FV to search\r
\r
@return Instance of PEI_CORE_FV_HANDLE.\r
**/\r
}\r
\r
/**\r
- Report the information for a new discovered FV in unknown third-party format.\r
+ Report the information for a newly discovered FV in an unknown format.\r
\r
- If the EFI_PEI_FIRMWARE_VOLUME_PPI has not been installed for third-party FV format, but\r
- the FV in this format has been discovered, then this FV's information will be cached into\r
- PEI_CORE_INSTANCE's UnknownFvInfo array.\r
- Also a notification would be installed for unknown third-party FV format guid, if EFI_PEI_FIRMWARE_VOLUME_PPI\r
- is installed later by platform's PEIM, the original unknown third-party FV will be processed by\r
+ If the EFI_PEI_FIRMWARE_VOLUME_PPI has not been installed for a third-party FV format, but\r
+ the FV has been discovered, then the information of this FV will be cached into PEI_CORE_INSTANCE's\r
+ UnknownFvInfo array.\r
+\r
+ Also a notification would be installed for unknown FV format GUID, if EFI_PEI_FIRMWARE_VOLUME_PPI\r
+ is installed later by platform's PEIM, the original unknown FV will be processed by\r
using new installed EFI_PEI_FIRMWARE_VOLUME_PPI.\r
\r
@param PrivateData Point to instance of PEI_CORE_INSTANCE\r
);\r
\r
/**\r
- Report the information for a new discovered FV in unknown format.\r
+ Report the information for a newly discovered FV in an unknown format.\r
+\r
+ If the EFI_PEI_FIRMWARE_VOLUME_PPI has not been installed for a third-party FV format, but\r
+ the FV has been discovered, then the information of this FV will be cached into PEI_CORE_INSTANCE's\r
+ UnknownFvInfo array.\r
\r
- If the EFI_PEI_FIRMWARE_VOLUME_PPI has not been installed for specific FV format, but\r
- the FV in this FV format has been discovered, then the information of this FV\r
- will be cached into PEI_CORE_INSTANCE's UnknownFvInfo array.\r
Also a notification would be installed for unknown FV format GUID, if EFI_PEI_FIRMWARE_VOLUME_PPI\r
is installed later by platform's PEIM, the original unknown FV will be processed by\r
using new installed EFI_PEI_FIRMWARE_VOLUME_PPI.\r
/**\r
\r
Pool allocation service. Before permanent memory is discovered, the pool will\r
- be allocated the heap in the temporary memory. Generally, the size of heap in temporary\r
- memory does not exceed to 64K, so the biggest pool size could be allocated is\r
+ be allocated in the heap in temporary memory. Generally, the size of the heap in temporary\r
+ memory does not exceed 64K, so the biggest pool size could be allocated is\r
64K.\r
\r
@param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation.\r
//\r
\r
//\r
- // Generally, the size of heap in temporary memory does not exceed to 64K,\r
+ // Generally, the size of heap in temporary memory does not exceed 64K,\r
// HobLength is multiples of 8 bytes, so the maximum size of pool is 0xFFF8 - sizeof (EFI_HOB_MEMORY_POOL)\r
//\r
if (Size > (0xFFF8 - sizeof (EFI_HOB_MEMORY_POOL))) {\r
);\r
\r
/**\r
- This routine enable a PEIM to register itself to shadow when PEI Foundation\r
- discovery permanent memory.\r
+ This routine enables a PEIM to register itself for shadow when the PEI Foundation\r
+ discovers permanent memory.\r
\r
@param FileHandle File handle of a PEIM.\r
\r
);\r
\r
/**\r
- Get instance of PEI_CORE_FV_HANDLE for next volume according to given index.\r
+ Gets a PEI_CORE_FV_HANDLE instance for the next volume according to the given index.\r
\r
- This routine also will install FvInfo PPI for FV HOB in PI ways.\r
+ This routine also will install an instance of the FvInfo PPI for the FV HOB\r
+ as defined in the PI specification.\r
\r
@param Private Pointer of PEI_CORE_INSTANCE\r
- @param Instance The index of FV want to be searched.\r
+ @param Instance Index of the FV to search\r
\r
@return Instance of PEI_CORE_FV_HANDLE.\r
**/\r