UEFI规范详解:引导流程与GPT介绍

需积分: 22 2 下载量 79 浏览量 更新于2024-07-24 收藏 9.76MB PDF 举报
"uefi_spec.pdf" 是一份关于 Unified Extensible Firmware Interface (UEFI) 规范的文档,版本为 2.3.1,发布日期为2011年4月6日。这份文档详细描述了EFI(Extensible Firmware Interface)和GPT(GUID Partition Table)在计算机启动过程中的应用。 UEFI 是一种现代的、更加先进的固件接口,取代了传统的BIOS(Basic Input/Output System),为操作系统提供了一个标准化的平台来初始化硬件并控制系统的启动流程。它的主要目标是提高系统的安全性、性能和可扩展性。与BIOS相比,UEFI提供了图形化的用户界面,支持更大的磁盘分区和更快速的启动时间。 GPT是UEFI环境中常用的硬盘分区表格式,替代了传统的MBR(Master Boot Record)。GPT允许最多定义128个主分区,并且支持最大18EB的磁盘容量,远超MBR的限制。每个GPT分区都有一个全局唯一标识符(GUID),这使得分区识别更加安全和可靠,尤其是在多系统或动态磁盘管理场景下。 在EFI启动流程中,首先由固件执行初始化,包括硬件检测、加载配置和驱动程序。然后,UEFI固件会查找并加载引导程序,这个程序可以是操作系统的一部分或者是单独的引导管理器。引导程序负责加载操作系统内核到内存中。UEFI还支持Secure Boot特性,可以防止未经授权的固件或操作系统加载,增强了系统的安全性。 UEFI规范中,"保留"或"未定义"的特征是留给未来扩展的,设计者不应依赖这些特性,因为它们可能会在后续版本中改变或者被赋予新的功能。文档特别指出,所有信息都是“按原样”提供的,不包含任何明示或暗示的保修,包括但不限于对适销性、特定用途适用性、响应的准确性或完整性、结果、工作质量、无病毒和无过失的保修。 UEFI规范2.3.1版为计算机制造商和软件开发者提供了详细的指导,以实现高效、安全的系统启动和管理。它涵盖了固件接口的设计、功能、以及与操作系统的交互,对于理解现代计算机系统的底层工作原理至关重要。
2020-03-11 上传
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.
2020-03-11 上传
This Unified Extensible Firmware Interface (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.