2 PI PEI master include file. This file should match the PI spec.
4 Copyright (c) 2006 - 2009, Intel Corporation
5 All rights reserved. This program and the accompanying materials
6 are licensed and made available under the terms and conditions of the BSD License
7 which accompanies this distribution. The full text of the license may be found at
8 http://opensource.org/licenses/bsd-license.php
10 THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS,
11 WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED.
13 @par Revision Reference:
18 #ifndef __PI_PEICIS_H__
19 #define __PI_PEICIS_H__
21 #include <Uefi/UefiMultiPhase.h>
22 #include <Pi/PiMultiPhase.h>
25 /// Handles of EFI FV.
27 typedef VOID
*EFI_PEI_FV_HANDLE
;
30 /// Handles of EFI FFS
32 typedef VOID
*EFI_PEI_FILE_HANDLE
;
35 /// Declare forward reference data structure for EFI_PEI_SERVICE
37 typedef struct _EFI_PEI_SERVICES EFI_PEI_SERVICES
;
40 /// Declare forward reference data structure for EFI_PEI_NOTIFY_DESCRIPTOR
42 typedef struct _EFI_PEI_NOTIFY_DESCRIPTOR EFI_PEI_NOTIFY_DESCRIPTOR
;
45 #include <Ppi/CpuIo.h>
46 #include <Ppi/PciCfg2.h>
50 The PEI Dispatcher will invoke each PEIM one time. During this pass, the PEI
51 Dispatcher will pass control to the PEIM at the AddressOfEntryPoint in the PE Header.
53 @param FileHandle Pointer to the FFS file header.
54 @param PeiServices Describes the list of possible PEI Services.
56 @retval EFI_SUCCESS The PEI completed successfully.
57 @retval !EFI_SUCCESS There is error in PEIM.
62 (EFIAPI
*EFI_PEIM_ENTRY_POINT2
)(
63 IN EFI_PEI_FILE_HANDLE FileHandle
,
64 IN CONST EFI_PEI_SERVICES
**PeiServices
68 Entry point of the notification callback function itself within the PEIM.
70 @param PeiServices Indirect reference to the PEI Services Table.
71 @param NotifyDescriptor Address of the notification descriptor data structure.
72 @param Ppi Address of the PPI that was installed.
74 @return Status of the notification.
78 (EFIAPI
*EFI_PEIM_NOTIFY_ENTRY_POINT
)(
79 IN EFI_PEI_SERVICES
**PeiServices
,
80 IN EFI_PEI_NOTIFY_DESCRIPTOR
*NotifyDescriptor
,
85 // PEI Ppi Services List Descriptors
87 #define EFI_PEI_PPI_DESCRIPTOR_PIC 0x00000001
88 #define EFI_PEI_PPI_DESCRIPTOR_PPI 0x00000010
89 #define EFI_PEI_PPI_DESCRIPTOR_NOTIFY_CALLBACK 0x00000020
90 #define EFI_PEI_PPI_DESCRIPTOR_NOTIFY_DISPATCH 0x00000040
91 #define EFI_PEI_PPI_DESCRIPTOR_NOTIFY_TYPES 0x00000060
92 #define EFI_PEI_PPI_DESCRIPTOR_TERMINATE_LIST 0x80000000
95 /// The data structure through which a PEIM describes available services to the PEI Foundation.
99 /// This field is a set of flags describing the characteristics of this imported table entry.
100 /// All flags are defined as EFI_PEI_PPI_DESCRIPTOR_***, which can also be combined into one.
104 /// The address of the EFI_GUID that names the interface.
108 /// A pointer to the PPI. It contains the information necessary to install a service.
111 } EFI_PEI_PPI_DESCRIPTOR
;
114 /// The data structure in a given PEIM that tells the PEI
115 /// Foundation where to invoke the notification service.
117 struct _EFI_PEI_NOTIFY_DESCRIPTOR
{
119 /// Details if the type of notification is callback or dispatch.
123 /// The address of the EFI_GUID that names the interface.
127 /// Address of the notification callback function itself within the PEIM.
129 EFI_PEIM_NOTIFY_ENTRY_POINT Notify
;
133 This service is the first one provided by the PEI Foundation. This function
134 installs an interface in the PEI PPI database by GUID. The purpose of the
135 service is to publish an interface that other parties can use to call
138 @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table
139 published by the PEI Foundation.
140 @param PpiList A pointer to the list of interfaces that the caller shall install.
142 @retval EFI_SUCCESS The interface was successfully installed.
143 @retval EFI_INVALID_PARAMETER The PpiList pointer is NULL or Any of the PEI PPI descriptors in the list do not have the EFI_PEI_PPI_DESCRIPTOR_PPI bit set in the Flags field.
144 @retval EFI_OUT_OF_RESOURCES There is no additional space in the PPI database.
149 (EFIAPI
*EFI_PEI_INSTALL_PPI
)(
150 IN CONST EFI_PEI_SERVICES
**PeiServices
,
151 IN CONST EFI_PEI_PPI_DESCRIPTOR
*PpiList
155 This function reinstalls an interface in the PEI PPI database by GUID.
156 The purpose of the service is to publish an interface that other parties
157 can use to replace a same-named interface in the protocol database
158 with a different interface.
160 @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table
161 published by the PEI Foundation.
162 @param OldPpi A pointer to the former PPI in the database.
163 @param NewPpi A pointer to the new interfaces that the caller shall install.
165 @retval EFI_SUCCESS The interface was successfully installed.
166 @retval EFI_INVALID_PARAMETER The PpiList pointer is NULL or Any of the PEI PPI descriptors in the
167 list do not have the EFI_PEI_PPI_DESCRIPTOR_PPI bit set in the Flags field.
168 @retval EFI_OUT_OF_RESOURCES There is no additional space in the PPI database.
169 @retval EFI_NOT_FOUND The PPI for which the reinstallation was requested has not been installed.
174 (EFIAPI
*EFI_PEI_REINSTALL_PPI
)(
175 IN CONST EFI_PEI_SERVICES
**PeiServices
,
176 IN CONST EFI_PEI_PPI_DESCRIPTOR
*OldPpi
,
177 IN CONST EFI_PEI_PPI_DESCRIPTOR
*NewPpi
181 This function locates an interface in the PEI PPI database by GUID.
183 @param PeiServices An indirect pointer to the EFI_PEI_SERVICES published by the PEI Foundation.
184 @param Guid A pointer to the GUID whose corresponding interface needs to be found.
185 @param Instance The N-th instance of the interface that is required.
186 @param PpiDescriptor A pointer to instance of the EFI_PEI_PPI_DESCRIPTOR.
187 @param Ppi A pointer to the instance of the interface.
189 @retval EFI_SUCCESS The interface was successfully returned.
190 @retval EFI_NOT_FOUND The PPI descriptor is not found in the database.
195 (EFIAPI
*EFI_PEI_LOCATE_PPI
)(
196 IN CONST EFI_PEI_SERVICES
**PeiServices
,
197 IN CONST EFI_GUID
*Guid
,
199 IN OUT EFI_PEI_PPI_DESCRIPTOR
**PpiDescriptor OPTIONAL
,
204 This function installs a notification service to be called back when a
205 given interface is installed or reinstalled. The purpose of the service
206 is to publish an interface that other parties can use to call additional PPIs
207 that may materialize later.
209 @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation
210 @param NotifyList A pointer to the list of notification interfaces that the caller shall install.
212 @retval EFI_SUCCESS The interface was successfully installed.
213 @retval EFI_INVALID_PARAMETER The PpiList pointer is NULL or Any of the PEI PPI descriptors in the
214 list do not have the EFI_PEI_PPI_DESCRIPTOR_PPI bit set in the Flags field.
215 @retval EFI_OUT_OF_RESOURCES There is no additional space in the PPI database.
220 (EFIAPI
*EFI_PEI_NOTIFY_PPI
)(
221 IN CONST EFI_PEI_SERVICES
**PeiServices
,
222 IN CONST EFI_PEI_NOTIFY_DESCRIPTOR
*NotifyList
226 This function returns the present value of the boot mode.
228 @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation.
229 @param BootMode A pointer to contain the value of the boot mode.
231 @retval EFI_SUCCESS The boot mode was returned successfully.
236 (EFIAPI
*EFI_PEI_GET_BOOT_MODE
)(
237 IN CONST EFI_PEI_SERVICES
**PeiServices
,
238 OUT EFI_BOOT_MODE
*BootMode
242 This function sets the value of the boot mode.
244 @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation
245 @param BootMode The value of the boot mode to set.
247 @retval EFI_SUCCESS The boot mode was returned successfully.
252 (EFIAPI
*EFI_PEI_SET_BOOT_MODE
)(
253 IN CONST EFI_PEI_SERVICES
**PeiServices
,
254 IN EFI_BOOT_MODE BootMode
258 This function returns the pointer to the list of Hand-Off Blocks (HOBs) in memory.
260 @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation
261 @param HobList A pointer to the list of HOBs that the PEI Foundation will initialize
263 @retval EFI_SUCCESS The list was successfully returned.
264 @retval EFI_NOT_AVAILABLE_YET The HOB list is not yet published.
269 (EFIAPI
*EFI_PEI_GET_HOB_LIST
)(
270 IN CONST EFI_PEI_SERVICES
**PeiServices
,
275 This service published by the PEI Foundation abstracts the creation of a Hand-Off Block's (HOB's) headers.
277 @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation.
278 @param Type The type of HOB to be installed.
279 @param Length The length of the HOB to be added.
280 @param Hob The address of a pointer that will contain the HOB header.
282 @retval EFI_SUCCESS The HOB was successfully created.
283 @retval EFI_OUT_OF_RESOURCES There is no additional space for HOB creation.
288 (EFIAPI
*EFI_PEI_CREATE_HOB
)(
289 IN CONST EFI_PEI_SERVICES
**PeiServices
,
296 The purpose of the service is to abstract the capability of the PEI
297 Foundation to discover instances of firmware volumes in the system.
299 This service enables PEIMs to discover additional firmware volumes. The PEI Foundation uses this
300 service to abstract the locations and formats of various firmware volumes. These volumes include
301 the Boot Firmware Volume and any other volumes exposed by EFI_PEI_FV_PPI. The service
302 returns a volume handle of type EFI_PEI_FV_HANDLE, which must be unique within the system.
304 @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation.
305 @param Instance This instance of the firmware volume to find.
306 The value 0 is the Boot Firmware Volume (BFV).
307 @param VolumeHandle On exit, points to the next volumn handle or NULL if it does not exist.
309 @retval EFI_SUCCESS The volume was found.
310 @retval EFI_NOT_FOUND The volume was not found.
311 @retval EFI_INVALID_PARAMETER VolumeHandle is NULL.
316 (EFIAPI
*EFI_PEI_FFS_FIND_NEXT_VOLUME2
)(
317 IN CONST EFI_PEI_SERVICES
**PeiServices
,
319 OUT EFI_PEI_FV_HANDLE
*VolumeHandle
323 Searches for the next matching file in the firmware volume.
325 This service enables PEIMs to discover firmware files within a specified volume.
326 To find the first instance of a firmware file, pass a FileHandle value of NULL into the service.
327 The service returns a file handle of type EFI_PEI_FILE_HANDLE, which must be unique within
330 @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation.
331 @param SearchType A filter to find files only of this type.
332 @param FvHandle Handle of firmware volume in which to search.
333 @param FileHandle On entry, points to the current handle from which to begin searching
334 or NULL to start at the beginning of the firmware volume.
335 On exit, points the file handle of the next file in the volume or NULL
336 if there are no more files.
338 @retval EFI_SUCCESS The file was found.
339 @retval EFI_NOT_FOUND The file was not found.
340 @retval EFI_NOT_FOUND The header checksum was not zero.
345 (EFIAPI
*EFI_PEI_FFS_FIND_NEXT_FILE2
)(
346 IN CONST EFI_PEI_SERVICES
**PeiServices
,
347 IN EFI_FV_FILETYPE SearchType
,
348 IN CONST EFI_PEI_FV_HANDLE FvHandle
,
349 IN OUT EFI_PEI_FILE_HANDLE
*FileHandle
353 Searches for the next matching section within the specified file.
355 This service enables PEI modules to discover the first section of a given type within a valid file.
356 This service will search within encapsulation sections (compression and GUIDed) as well. It will
357 search inside of a GUIDed section or a compressed section, but may not, for example, search a
358 GUIDed section inside a GUIDes section.
359 This service will not search within compression sections or GUIDed sections which require
360 extraction if memory is not present.
362 @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation.
363 @param SectionType The value of the section type to find.
364 @param FileHandle Handle of the firmware file to search.
365 @param SectionData A pointer to the discovered section, if successful.
367 @retval EFI_SUCCESS The section was found.
368 @retval EFI_NOT_FOUND The section was not found.
373 (EFIAPI
*EFI_PEI_FFS_FIND_SECTION_DATA2
)(
374 IN CONST EFI_PEI_SERVICES
**PeiServices
,
375 IN EFI_SECTION_TYPE SectionType
,
376 IN EFI_PEI_FILE_HANDLE FileHandle
,
377 OUT VOID
**SectionData
381 This function registers the found memory configuration with the PEI Foundation.
383 @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation.
384 @param MemoryBegin The value of a region of installed memory
385 @param MemoryLength The corresponding length of a region of installed memory.
387 @retval EFI_SUCCESS The region was successfully installed in a HOB.
388 @retval EFI_INVALID_PARAMETER MemoryBegin and MemoryLength are illegal for this system.
389 @retval EFI_OUT_OF_RESOURCES There is no additional space for HOB creation.
394 (EFIAPI
*EFI_PEI_INSTALL_PEI_MEMORY
)(
395 IN CONST EFI_PEI_SERVICES
**PeiServices
,
396 IN EFI_PHYSICAL_ADDRESS MemoryBegin
,
397 IN UINT64 MemoryLength
401 The purpose of the service is to publish an interface that allows
402 PEIMs to allocate memory ranges that are managed by the PEI Foundation.
404 @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation.
405 @param MemoryType The type of memory to allocate.
406 @param Pages The number of contiguous 4 KB pages to allocate.
407 @param Memory Pointer to a physical address. On output, the address is set to the base
408 of the page range that was allocated.
410 @retval EFI_SUCCESS The memory range was successfully allocated.
411 @retval EFI_OUT_OF_RESOURCES The pages could not be allocated.
412 @retval EFI_INVALID_PARAMETER Type is not equal to AllocateAnyPages.
417 (EFIAPI
*EFI_PEI_ALLOCATE_PAGES
)(
418 IN CONST EFI_PEI_SERVICES
**PeiServices
,
419 IN EFI_MEMORY_TYPE MemoryType
,
421 OUT EFI_PHYSICAL_ADDRESS
*Memory
425 The purpose of this service is to publish an interface that
426 allows PEIMs to allocate memory ranges that are managed by the PEI Foundation.
428 @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation.
429 @param Size The number of bytes to allocate from the pool.
430 @param Buffer If the call succeeds, a pointer to a pointer to the allocated buffer; undefined otherwise.
432 @retval EFI_SUCCESS The allocation was successful.
433 @retval EFI_OUT_OF_RESOURCES There is not enough heap to allocate the requested size.
438 (EFIAPI
*EFI_PEI_ALLOCATE_POOL
)(
439 IN CONST EFI_PEI_SERVICES
**PeiServices
,
445 This service copies the contents of one buffer to another buffer.
447 @param Destination Pointer to the destination buffer of the memory copy.
448 @param Source Pointer to the source buffer of the memory copy
449 @param Length Number of bytes to copy from Source to Destination.
454 (EFIAPI
*EFI_PEI_COPY_MEM
)(
455 IN VOID
*Destination
,
461 The service fills a buffer with a specified value.
463 @param Buffer Pointer to the buffer to fill.
464 @param Size Number of bytes in Buffer to fill.
465 @param Value Value to fill Buffer with
470 (EFIAPI
*EFI_PEI_SET_MEM
)(
477 This service publishes an interface that allows PEIMs to report status codes.
479 ReportStatusCode() is called by PEIMs that wish to report status information on their
480 progress. The principal use model is for a PEIM to emit one of the standard 32-bit error codes. This
481 will allow a platform owner to ascertain the state of the system, especially under conditions where
482 the full consoles might not have been installed.
484 @param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation.
485 @param Type Indicates the type of status code being reported.
486 @param Value Describes the current status of a hardware or
487 software entity. This includes information about the class and
488 subclass that is used to classify the entity as well as an operation.
489 For progress codes, the operation is the current activity.
490 For error codes, it is the exception.For debug codes,it is not defined at this time.
491 @param Instance The enumeration of a hardware or software entity within
492 the system. A system may contain multiple entities that match a class/subclass
493 pairing. The instance differentiates between them. An instance of 0 indicates
494 that instance information is unavailable, not meaningful, or not relevant.
495 Valid instance numbers start with 1.
496 @param CallerId This optional parameter may be used to identify the caller.
497 This parameter allows the status code driver to apply different rules to
499 @param Data This optional parameter may be used to pass additional data.
501 @retval EFI_SUCCESS The function completed successfully.
502 @retval EFI_NOT_AVAILABLE_YET No progress code provider has installed an interface in the system.
507 (EFIAPI
*EFI_PEI_REPORT_STATUS_CODE
)(
508 IN CONST EFI_PEI_SERVICES
**PeiServices
,
509 IN EFI_STATUS_CODE_TYPE Type
,
510 IN EFI_STATUS_CODE_VALUE Value
,
512 IN CONST EFI_GUID
*CallerId OPTIONAL
,
513 IN CONST EFI_STATUS_CODE_DATA
*Data OPTIONAL
517 Resets the entire platform.
519 This service resets the entire platform, including all processors
520 and devices, and reboots the system.
521 This service will never return EFI_SUCCESS.
523 @param PeiServices An indirect pointer to the EFI_PEI_SERVICES
524 table published by the PEI Foundation.
526 @retval EFI_NOT_AVAILABLE_YET The service has not been installed yet.
531 (EFIAPI
*EFI_PEI_RESET_SYSTEM
)(
532 IN CONST EFI_PEI_SERVICES
**PeiServices
536 Find a file within a volume by its name.
538 This service searches for files with a specific name, within
539 either the specified firmware volume or all firmware volumes.
540 The service returns a file handle of type EFI_PEI_FILE_HANDLE,
541 which must be unique within the system.
543 @param FileName A pointer to the name of the file to
544 find within the firmware volume.
545 @param VolumeHandle The firmware volume to search.
546 @param FileHandle Upon exit, points to the found file's
547 handle or NULL if it could not be found.
549 @retval EFI_SUCCESS File was found.
550 @retval EFI_NOT_FOUND File was not found.
551 @retval EFI_INVALID_PARAMETER VolumeHandle or FileHandle or
557 (EFIAPI
*EFI_PEI_FFS_FIND_BY_NAME
)(
558 IN CONST EFI_GUID
*FileName
,
559 IN EFI_PEI_FV_HANDLE VolumeHandle
,
560 OUT EFI_PEI_FILE_HANDLE
*FileHandle
564 /// Information of FV file.
568 /// Name of the file.
574 EFI_FV_FILETYPE FileType
;
576 /// Attributes of the file.
578 EFI_FV_FILE_ATTRIBUTES FileAttributes
;
580 /// Points to the file's data (not the header).
581 /// Not valid if EFI_FV_FILE_ATTRIB_MEMORY_MAPPED
586 /// Size of the file's data.
592 Returns information about a specific file.
594 This function returns information about a specific file,
595 including its file name, type, attributes, starting address and
596 size. If the firmware volume is not memory mapped then the
597 Buffer member will be NULL.
599 @param FileHandle Handle of the file.
600 @param FileInfo Upon exit, points to the file's
603 @retval EFI_SUCCESS File information returned.
604 @retval EFI_INVALID_PARAMETER If FileHandle does not
605 represent a valid file.
606 @retval EFI_INVALID_PARAMETER If FileInfo is NULL.
611 (EFIAPI
*EFI_PEI_FFS_GET_FILE_INFO
)(
612 IN EFI_PEI_FILE_HANDLE FileHandle
,
613 OUT EFI_FV_FILE_INFO
*FileInfo
617 /// Information of FV volume.
621 /// Attributes of the firmware volume.
623 EFI_FVB_ATTRIBUTES_2 FvAttributes
;
625 /// Format of the firmware volume.
629 /// Name of the firmware volume.
633 /// Points to the first byte of the firmware
634 /// volume, if bit EFI_FVB_MEMORY_MAPPED is
635 /// set in FvAttributes.
639 /// Size of the firmware volume.
645 Returns information about the specified volume.
647 This function returns information about a specific firmware
648 volume, including its name, type, attributes, starting address
651 @param VolumeHandle Handle of the volume.
653 @param VolumeInfo Upon exit, points to the volume's
656 @retval EFI_SUCCESS File information returned.
657 @retval EFI_INVALID_PARAMETER If FileHandle does not
658 represent a valid file.
659 @retval EFI_INVALID_PARAMETER If FileInfo is NULL.
664 (EFIAPI
*EFI_PEI_FFS_GET_VOLUME_INFO
)(
665 IN EFI_PEI_FV_HANDLE VolumeHandle
,
666 OUT EFI_FV_INFO
*VolumeInfo
670 Register a PEIM so that it will be shadowed and called again.
672 This service registers a file handle so that after memory is
673 available, the PEIM will be re-loaded into permanent memory and
674 re-initialized. The PEIM registered this way will always be
675 initialized twice. The first time, this function call will
676 return EFI_SUCCESS. The second time, this function call will
677 return EFI_ALREADY_STARTED. Depending on the order in which
678 PEIMs are dispatched, the PEIM making this call may be
679 initialized after permanent memory is installed, even the first
682 @param FileHandle PEIM's file handle. Must be the currently
685 @retval EFI_SUCCESS The PEIM was successfully registered for
687 @retval EFI_ALREADY_STARTED The PEIM was previously
688 registered for shadowing.
689 @retval EFI_NOT_FOUND The FileHandle does not refer to a
695 (EFIAPI
*EFI_PEI_REGISTER_FOR_SHADOW
)(
696 IN EFI_PEI_FILE_HANDLE FileHandle
701 // PEI Specification Revision information
703 #define PEI_SPECIFICATION_MAJOR_REVISION 1
704 #define PEI_SPECIFICATION_MINOR_REVISION 0
706 /// Inconsistent with specification here:
707 /// In PI1.0 spec, PEI_SERVICES_SIGNATURE is defined as 0x5652455320494550. But
708 /// to pass multiple tool chain, it is append a ULL.
711 // PEI Services Table
713 #define PEI_SERVICES_SIGNATURE 0x5652455320494550ULL
715 /// Inconsistent with specification here:
716 /// In PI1.0 spec, There is a typo error in PEI_SERVICES_REVISION. In the spec. the defintion is
717 /// #define ((PEI_SPECIFICATION_MAJOR_REVISION<<16) |(PEI_SPECIFICATION_MINOR_REVISION))
718 /// and it should be as follow:
720 #define PEI_SERVICES_REVISION ((PEI_SPECIFICATION_MAJOR_REVISION<<16) | (PEI_SPECIFICATION_MINOR_REVISION))
723 /// EFI_PEI_SERVICES is a collection of functions whose implementation is provided by the PEI
724 /// Foundation. These services fall into various classes, including the following:
725 /// - Managing the boot mode
726 /// - Allocating both early and permanent memory
727 /// - Supporting the Firmware File System (FFS)
728 /// - Abstracting the PPI database abstraction
729 /// - Creating Hand-Off Blocks (HOBs)
731 struct _EFI_PEI_SERVICES
{
733 /// The table header for the PEI Services Table.
735 EFI_TABLE_HEADER Hdr
;
740 EFI_PEI_INSTALL_PPI InstallPpi
;
741 EFI_PEI_REINSTALL_PPI ReInstallPpi
;
742 EFI_PEI_LOCATE_PPI LocatePpi
;
743 EFI_PEI_NOTIFY_PPI NotifyPpi
;
746 // Boot Mode Functions
748 EFI_PEI_GET_BOOT_MODE GetBootMode
;
749 EFI_PEI_SET_BOOT_MODE SetBootMode
;
754 EFI_PEI_GET_HOB_LIST GetHobList
;
755 EFI_PEI_CREATE_HOB CreateHob
;
758 // Firmware Volume Functions
760 EFI_PEI_FFS_FIND_NEXT_VOLUME2 FfsFindNextVolume
;
761 EFI_PEI_FFS_FIND_NEXT_FILE2 FfsFindNextFile
;
762 EFI_PEI_FFS_FIND_SECTION_DATA2 FfsFindSectionData
;
765 // PEI Memory Functions
767 EFI_PEI_INSTALL_PEI_MEMORY InstallPeiMemory
;
768 EFI_PEI_ALLOCATE_PAGES AllocatePages
;
769 EFI_PEI_ALLOCATE_POOL AllocatePool
;
770 EFI_PEI_COPY_MEM CopyMem
;
771 EFI_PEI_SET_MEM SetMem
;
776 EFI_PEI_REPORT_STATUS_CODE ReportStatusCode
;
781 EFI_PEI_RESET_SYSTEM ResetSystem
;
784 // (the following interfaces are installed by publishing PEIM)
787 EFI_PEI_CPU_IO_PPI
*CpuIo
;
788 EFI_PEI_PCI_CFG2_PPI
*PciCfg
;
791 // Future Installed Services
793 EFI_PEI_FFS_FIND_BY_NAME FfsFindFileByName
;
794 EFI_PEI_FFS_GET_FILE_INFO FfsGetFileInfo
;
795 EFI_PEI_FFS_GET_VOLUME_INFO FfsGetVolumeInfo
;
796 EFI_PEI_REGISTER_FOR_SHADOW RegisterForShadow
;
801 /// EFI_SEC_PEI_HAND_OFF structure hold information about
802 /// PEI core's operating environment, such as the size of location of
803 /// temporary RAM, the stack location and BFV location.
805 typedef struct _EFI_SEC_PEI_HAND_OFF
{
807 /// Size of the data structure.
812 /// Points to the first byte of the boot firmware volume,
813 /// which the PEI Dispatcher should search for
816 VOID
*BootFirmwareVolumeBase
;
819 /// Size of the boot firmware volume, in bytes.
821 UINTN BootFirmwareVolumeSize
;
824 /// Points to the first byte of the temporary RAM.
826 VOID
*TemporaryRamBase
;
829 /// Size of the temporary RAM, in bytes.
831 UINTN TemporaryRamSize
;
834 /// Points to the first byte of the temporary RAM
835 /// available for use by the PEI Foundation. The area
836 /// described by PeiTemporaryRamBase and PeiTemporaryRamSize
837 /// must not extend outside beyond the area described by
838 /// TemporaryRamBase & TemporaryRamSize. This area should not
839 /// overlap with the area reported by StackBase and
842 VOID
*PeiTemporaryRamBase
;
845 /// Size of the available temporary RAM available for
846 /// use by the PEI Foundation, in bytes.
848 UINTN PeiTemporaryRamSize
;
851 /// Points to the first byte of the stack.
852 /// This are may be part of the memory described by
853 /// TemporaryRamBase and TemporaryRamSize
854 /// or may be an entirely separate area.
859 /// Size of the stack, in bytes.
862 } EFI_SEC_PEI_HAND_OFF
;
866 Entry point of PEI Foundation.
868 This function is the entry point for the PEI Foundation, which
869 allows the SEC phase to pass information about the stack,
870 temporary RAM and the Boot Firmware Volume. In addition, it also
871 allows the SEC phase to pass services and data forward for use
872 during the PEI phase in the form of one or more PPIs. There is
873 no limit to the number of additional PPIs that can be passed
874 from SEC into the PEI Foundation. As part of its initialization
875 phase, the PEI Foundation will add these SEC-hosted PPIs to its
876 PPI database such that both the PEI Foundation and any modules
877 can leverage the associated service calls and/or code in these
880 @param SecCoreData Points to a data structure containing
881 information about the PEI core's
882 operating environment, such as the size
883 and location of temporary RAM, the stack
884 location and the BFV location.
886 @param PpiList Points to a list of one or more PPI
887 descriptors to be installed initially by
888 the PEI core. An empty PPI list consists
889 of a single descriptor with the end-tag
890 EFI_PEI_PPI_DESCRIPTOR_TERMINATE_LIST.
891 As part of its initialization phase, the
892 PEI Foundation will add these SEC-hosted
893 PPIs to its PPI database such that both
894 the PEI Foundation and any modules can
895 leverage the associated service calls
896 and/or code in these early PPIs.
902 (EFIAPI
*EFI_PEI_CORE_ENTRY_POINT
)(
903 IN CONST EFI_SEC_PEI_HAND_OFF
*SecCoreData
,
904 IN CONST EFI_PEI_PPI_DESCRIPTOR
*PpiList