UEFI PI 规范1.7--- 4 Services - PEI

4 Services - PEI

4.1 Introduction

 A PEI Service is defined as a function, command, or other capability created by the PEI Foundation
during a phase that remains available after the phase is complete. Because the PEI phase has no
permanent memory available until nearly the end of the phase, the range of PEI Foundation Services
created during the PEI phase cannot be as rich as those created during later phases.
Table 5 shows the PEI Services described in this section:

PEI Service是由PEI Foundation创建的一组功能或者命令或者其他的能力,并且在PEI Foundation完成后仍可以继续使用。因为在PEI阶段是没有可以使用的永久内存的,直到PEI阶段的末尾才有,PEI阶段创建的PEI Foundation Services不如后面几个阶段来的丰富。
Table 5. PEI Services

PPI Services:

Manages PEIM-to-PEIM Interface (PPIs) to facilitate intermodule calls
between PEIMs. Interfaces are installed and tracked on a database
maintained in temporary RAM.

管理PEIM到PEIM之间的接口(PPIs)来方便PEIM内部间的交流和调用。接口的安装和查找在处于临时内存的database中。

Boot Mode Services:

Manages the boot mode (S3, S5, normal boot, diagnostics, etc.) of the
system.

管理系统的启动模式(S3 S5 通常启动 诊断)

HOB Services:

Creates data structures called Hand-Off Blocks (HOBs) that are used to
pass information to the next phase of the PI Architecture.

创建一个称为HOBs的数据结构,在PI结构中用于传递信息到下一个阶段(DXE)。

Firmware Volume Services:

Walks the Firmware File Systems (FFS) in firmware volumes to find PEIMs
and other firmware files in the flash device.

在FV中的FFS里查找PEIM,以及其它在flash设备中的firmware文件

PEI Memory Services:

Provides a collection of memory management services for use both before
and after permanent memory has been discovered.

在永久内存被发现的前后,提供一组内存管理的服务。

Status Code Services:

Provides common progress and error code reporting services (for
example, port 080h or a serial port for simple text output for debug).

提供常见的进度和错误码报告服务(例如:0x80端口或串口进行简单的文本输出用于debug)。

Reset Services:

Provides a common means by which to initiate a warm or cold restart of
the system.

对于系统是冷启动还是热启动提供一组通用的初始化方法。

The calling convention for PEI Services is similar to PPIs. See “PEIM-to-PEIM Communication”
on page 116
for more details on PPIs.
The means by which to bind a service call into a service involves a dispatch table,
EFI_PEI_SERVICES.A pointer to the table is passed into the PEIM entry point.

调用PEI Services的俗称约定与PPI的类似。将服务调用绑定到服务的方法涉及到调度表EFI_PEI_SERVICES。指向表的指针被传递到PEIM入口点。

 

  • 0
    点赞
  • 2
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
This Unified Extensible Firmware Interface (hereafter known as UEFI) Specification describes an interface between the operating system (OS) and the platform firmware. UEFI was preceded by the Extensible Firmware Interface Specification 1.10 (EFI). As a result, some code and certain protocol names retain the EFI designation. Unless otherwise noted, EFI designations in this specification may be assumed to be part of UEFI. The interface is in the form of data tables that contain platform-related information, and boot and runtime service calls that are available to the OS loader and the OS. Together, these provide a standard environment for booting an OS. This specification is designed as a pure interface specification. As such, the specification defines the set of interfaces and structures that platform firmware must implement. Similarly, the specification defines the set of interfaces and structures that the OS may use in booting. How either the firmware developer chooses to implement the required elements or the OS developer chooses to make use of those interfaces and structures is an implementation decision left for the developer. The intent of this specification is to define a way for the OS and platform firmware to communicate only information necessary to support the OS boot process. This is accomplished through a formal and complete abstract specification of the software-visible interface presented to the OS by the platform and firmware. Using this formal definition, a shrink-wrap OS intended to run on platforms compatible with supported processor specifications will be able to boot on a variety of system designs without further platform or OS customization. The definition will also allow for platform innovation to introduce new features and functionality that enhance platform capability without requiring new code to be written in the OS boot sequence. Furthermore, an abstract specification opens a route to replace legacy devices and firmware code over time. New device types and associated code can provide equivalent functionality through the same defined abstract interface, again without impact on the OS boot support code. The specification is applicable to a full range of hardware platforms from mobile systems to servers. The specification provides a core set of services along with a selection of protocol interfaces. The selection of protocol interfaces can evolve over time to be optimized for various platform market segments. At the same time, the specification allows maximum extensibility and customization abilities for OEMs to allow differentiation. In this, the purpose of UEFI is to define an evolutionary path from the traditional “PC-AT”- style boot world into a legacy-API free environment.
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值