Advanced Configuration and Power Interface

From Wikipedia, the free encyclopedia - View original article

Jump to: navigation, search

In computing, the Advanced Configuration and Power Interface (ACPI) specification provides an open standard for device configuration and power management by the operating system.

First released in December 1996, ACPI defines platform-independent interfaces for hardware discovery, configuration, power management and monitoring. With the intention of replacing Advanced Power Management, the MultiProcessor Specification and the Plug and Play BIOS Specification,[1] the standard brings power management under the control of the operating system, as opposed to the previous BIOS-central system which relied on platform-specific firmware to determine power management and configuration policy.[2] The specification is central to Operating System-directed configuration and Power Management (OSPM), a system implementing ACPI which removes device management responsibilities from legacy firmware interfaces.

The standard was originally developed by Intel, Microsoft and Toshiba, and was later joined by HP and Phoenix. The latest version is "Revision 5.0", which was published on 6 December 2011.[3] As the ACPI technology gained wider adoption with many operating systems and processor architectures, the desire to improve the governance model of the specification has increased significantly. In October 2013, original developers of the ACPI standard agreed to transfer all assets to the UEFI Forum, where all future development will be taking place.[4]


The firmware-level ACPI has three main components: the ACPI tables, the ACPI BIOS and the ACPI registers. Unlike its predecessors, such as the APM or PnP BIOS, the ACPI implements little of its functionality in the ACPI BIOS code, whose main role is to load the ACPI tables in system memory. Instead, most of the firmware ACPI functionality is provided in ACPI Machine Language (AML) bytecode stored in the ACPI tables. To make use of these tables, the operating system must have an interpreter for the AML bytecode. A reference AML interpreter implementation is provided by the ACPI Component Architecture (ACPICA). At the BIOS development time, AML code is compiled from the ASL (ACPI Source Language) code.[5][6]

As ACPI also replaces PnP BIOS, it also provides a hardware enumerator, mostly implemented in the DSDT (Differentiated System Description Table) ACPI table. The advantage of a bytecode approach is that unlike PnP BIOS code (which was 16-bit), the ACPI bytecode may be used in any operating system, even in 64-bit long mode.[6]

Overall design decision was not without criticism. In November 2003, Linus Torvalds, initial creator of the Linux kernel, described ACPI as "a complete design disaster in every way".[7][8] In 2001, other senior Linux software developers like Alan Cox expressed concerns about the requirements that bytecode from an external source must be run by the kernel with full privileges, as well as the overall complexity of the ACPI specification.[9] In 2014, Mark Shuttleworth, founder of the Ubuntu Linux distribution, compared ACPI with trojan horses.[10]

ACPI Component Architecture (ACPICA)[edit]

The ACPI Component Architecture (ACPICA), mainly written by Intel's engineers, provides an open-source platform-independent reference implementation of the operating system–related ACPI code.[11] The ACPICA code is used by Linux, Haiku and FreeBSD,[5] which supplement it with their operating system–specific code.


The first revision of the ACPI specification was released in December 1996, supporting 16 and 32-bit addressing spaces. It was not until August 2000 that ACPI received 64-bit address support as well as support for multiprocessor workstations and servers with revision 2.0. In September 2004, revision 3.0 gave the ACPI specification support for SATA connectors, PCI Express bus, >256 multiprocessor support, ambient light sensors and user-presence devices, as well as extending the Thermal model beyond the previous processor-centric support. In June 2009, the 4.0 specification added many new features to the design; most notable are USB 3.0 support, logical processor idling support, and x2APIC support.[3] The latest of the major publications is revision 5.0, released in November 2011.[3]

Operating systems[edit]

Microsoft's Windows 98 was the first operating system to implement ACPI,[12][13] but its implementation was somewhat buggy or incomplete,[14][15] although some of the problems associated with it were caused by the first-generation ACPI hardware.[16] Other operating systems, including later versions of Windows, eComStation, FreeBSD, NetBSD, OpenBSD, HP-UX, OpenVMS, Linux, and PC versions of SunOS, have at least some support for ACPI.[17] Some newer operating systems like Windows Vista require ACPI-compliant BIOS to work at all[18] (in particular, Vista requires a BIOS with ACPI 2.0 or later).[19]

The 2.4 series of the Linux kernel had only minimal support for ACPI, with better support implemented (and enabled by default) from kernel version 2.6.0 onwards.[20] Old ACPI BIOS implementations tend to be quite buggy, and consequently are not supported by later operating systems. For example, Windows 2000, Windows XP, and Windows Server 2003 only use ACPI if the BIOS date is after January 1, 1999.[21] Similarly, Linux kernel 2.6 blacklisted any ACPI BIOS from before January 1, 2001.[20]

OSPM responsibilities[edit]

Once an OSPM-compatible operating system activates ACPI, it takes over and has exclusive control of all aspects of power management and device configuration. The OSPM implementation must expose an ACPI-compatible environment to device drivers, which exposes certain system, device and processor states.

Power states[edit]

Global states[edit]

The ACPI specification defines the following four Global "Gx" states and six Sleep "Sx" states for an ACPI-compliant computer-system:[22][23]

Furthermore, the specification defines a Legacy state: the state on an operating system which does not support ACPI. In this state, the hardware and power are not managed via ACPI, effectively disabling ACPI.

Device states[edit]

The device states D0D3 are device-dependent:

Processor states[edit]

The CPU power states C0C3 are defined as follows:

Performance states[edit]

While a device or processor operates (D0 and C0, respectively), it can be in one of several power-performance states. These states are implementation-dependent. Though, P0 is always the highest-performance state; with P1 to Pn being successively lower-performance states, up to an implementation-specific limit of n no greater than 16.

P-states have become known as SpeedStep in Intel processors, as PowerNow! or Cool'n'Quiet in AMD processors, and as PowerSaver in VIA processors.

Hardware interface[edit]

ACPI-compliant systems interact with hardware through either a "Function Fixed Hardware (FFH) Interface", or a platform-independent hardware programming model which relies on platform-specific ACPI Machine Language (AML) provided by the original equipment manufacturer (OEM).

Function Fixed Hardware interfaces are platform-specific features, provided by platform manufacturers for the purposes of performance and failure recovery. Standard Intel-based PCs have a fixed function interface defined by Intel,[26] which provides a set of core functionality that reduces an ACPI-compliant system's need for full driver stacks for providing basic functionality during boot time or in the case of major system failure.

Firmware interface[edit]

ACPI defines a large number of tables that provide the interface between an ACPI-compliant operating system, and system firmware. For example:[27]

The tables allow description of system hardware in a platform-independent manner, and are presented as either fixed-formatted data structures or in AML. The main AML table is the DSDT (differentiated system description table).

The Root System Description Pointer is located in a platform-dependent manner, and describes the rest of the tables.

ACPI Platform Error Interface (APEI)[edit]

A specification for reporting of hardware errors e.g. from the chipset, to the operating system.

Security risk[edit]

Ubuntu Linux founder Mark Shuttleworth has likened ACPI to Trojan horses.[28] He has described proprietary firmware (firmware ACPI or any other firmware) as a security risk, saying that "firmware on your device is the NSA's best friend" and calling firmware (ACPI or non-ACPI) "a Trojan horse of monumental proportions". He has pointed out that low quality, closed source firmware is a major threat to system security:[7] "Your biggest mistake is to assume that the NSA is the only institution abusing this position of trust — in fact, it's reasonable to assume that all firmware is a cesspool of insecurity, courtesy of incompetence of the highest degree from manufacturers, and competence of the highest degree from a very wide range of such agencies".

As a solution to this problem, he has called for declarative firmware (ACPI or non-ACPI).[7] Firmware should be open-source so that the code can be checked and verified. Firmware should be declarative, meaning that it should describe "hardware linkage and dependencies" and should not include executable code.

See also[edit]


  1. ^ ACPI Overview
  2. ^ Microsoft Corporation, Intel Corporation (February 1996). "APM BIOS Specification". Microsoft Corporation. Retrieved 2010-07-02. 
  3. ^ a b c Hewlett-Packard, Intel Corporation, Microsoft, Phoenix Technologies, Toshiba (2011-12-06). "Advanced Configuration and Power Interface Specification (Revision 5.0)" (PDF). Retrieved 2013-11-17. 
  4. ^ "ACPI and UEFI forum join forces: here’s why it matters". 2013-11-13. Retrieved 2013-11-17. 
  5. ^ a b ACPI implementation on FreeBSD - Usenix
  6. ^ a b ACPI in Linux, 2005
  7. ^ a b c Linux Magazine issue 162, May 2014, page 9
  8. ^ Searls, Doc (2003-11-25). "Linus & the Lunatics, Part II". Linux Journal. Retrieved 2010-01-13. 
  9. ^ Corbet, Jonathan (2001-07-04). "Kernel development". weekly edition. Retrieved 2010-07-02. 
  10. ^ Linux Format n°184, June 2014, page 7.
  11. ^ ACPICA: ACPI Component Architecture
  12. ^ "Limitations When Using Microsoft Windows 98 on Compaq Armada Portables" (PDF). October 1998. p. 3. Retrieved 2014-01-27. 
  13. ^ "Windows 98 on ThinkPad systems - ThinkPad General". Retrieved 2014-01-27. [dead link]
  14. ^ Robert Cowart; Brian Knittel (2000). Using Microsoft Windows 2000 Professional. Que Publishing. p. 30. ISBN 978-0-7897-2125-9. 
  15. ^ Windows 98 Does Not Support ACPI Passive Cooling Mode
  16. ^
  17. ^ Therien, Guy (2000-01-06). "ACPI 2.0 Specification Technical Review, Intel Developer Forum" (ppt). Intel Corporation. Archived from the original on 21 July 2011. Retrieved 2011-08-21. 
  18. ^ Marshall, Allen. "ACPI in Windows Vista" (PPT). Microsoft Corporation. Retrieved 2010-07-02. 
  19. ^ David Karp (2008). Windows Vista Annoyances: Tips, Secrets, and Hacks for the Cranky Consumer. "O'Reilly Media, Inc.". p. 221. ISBN 978-0-596-52762-4. 
  20. ^ a b The State of ACPI in the Linux Kernel
  21. ^ ACPI BIOS
  22. ^ ACPI Spec Rev 5.0 - dated December 6, 2011
  23. ^ Anand Lal Shimpi (2012-10-05). "Intel's Haswell Architecture Analyzed". AnandTech. Retrieved 2013-10-20. 
  24. ^ Wasson, Scott (2005-02-21). "Intel's Pentium 4 600 series processors". The Tech Report. p. 2. 
  25. ^ "Processor Package and Core C-States". AnandTech. 2013-06-09. Retrieved 2013-10-20. 
  26. ^ Intel Corporation (September 2006). "Intel Processor Vendor-Specific ACPI" (PDF). Archived from the original on 2012-12-25. Retrieved 2014-10-05. 
  27. ^ Brown, Len (2005-07-20). "ACPI in Linux". Ottawa Linux Symposium (PDF). p. 3. CiteSeerX: 
  28. ^ Linux Format n°184, June 2014, page 7

External links[edit]

This article is based on material taken from the Free On-line Dictionary of Computing prior to 1 November 2008 and incorporated under the "relicensing" terms of the GFDL, version 1.3 or later.