LLMpediaThe first transparent, open encyclopedia generated by LLMs

ACPI

Generated by GPT-5-mini
Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Parent: Xfce Hop 5
Expansion Funnel Raw 97 → Dedup 0 → NER 0 → Enqueued 0
1. Extracted97
2. After dedup0 (None)
3. After NER0 ()
4. Enqueued0 ()
ACPI
NameACPI
DeveloperIntel; Microsoft; Toshiba; HP; IBM
Initial release1996
Operating systemMicrosoft Windows; Linux; FreeBSD; NetBSD; OpenBSD; Solaris; macOS; BeOS
Platformx86; x86-64; ARM; IA-64
LicenseProprietary; specification

ACPI is a firmware specification that defines hardware configuration and power management interfaces for modern personal computers. It provides a standardized method for Intel-based and other architectures to expose device configuration, thermal control, and power states to Microsoft Windows and various open-source operating systems such as Linux and FreeBSD. ACPI's coordination among vendors like Intel, Microsoft, Toshiba, HP Inc. and IBM enabled broad industry adoption across OEMs including Dell, Lenovo, Acer, ASUS, and Samsung.

History

The specification emerged in the mid-1990s amid work by Intel, Microsoft, and Toshiba to replace legacy interfaces such as Advanced Power Management and platform-specific BIOS extensions used by vendors like Compaq and IBM PC. ACPI 1.0 debuted during the era of Windows 95 and Windows NT, while subsequent revisions coincided with processor families from Intel Pentium to Intel Core and server designs from AMD such as Athlon and Opteron. The specification evolved through collaboration with standards bodies and OEM consortiums that included HP, Fujitsu, NEC, Sony, and Toshiba, and saw integration with open-source projects led by communities around Red Hat, Canonical, and the Debian Project. Over time ACPI intersected with platform management efforts from UEFI and firmware initiatives tied to Intel Management Engine and ARM Trusted Firmware.

Architecture and Components

ACPI defines tables, methods, and objects exposed by system firmware and consumed by operating systems and hypervisors such as Xen Project, KVM, and VMware. Key components include the Root System Description Pointer used by OEM firmware from vendors like Phoenix Technologies and AMI to locate tables such as the Differentiated System Description Table and Fixed ACPI Description Table. The language layer, ACPI Machine Language, allows bytecode interpreted by AML interpreters implemented in Microsoft Windows NT, the Linux kernel, and projects maintained by NetBSD and OpenBSD. Device discoverability ties into buses and standards like PCI Express, USB, SATA, and Thunderbolt as implemented by manufacturers including Intel and NVIDIA. ACPI also interacts with platform features from Intel vPro, Trusted Platform Module, and ACPI-aware embedded controllers found in systems from Apple Inc. and Lenovo.

Power Management Features

ACPI specifies global system states (commonly S0–S5), processor C-states and P-states, and device-specific power states relied upon by operating systems such as Microsoft Windows 10, Linux kernel, and FreeBSD. Power-aware features coordinate with thermal management and hardware telemetry produced by vendors including Intel and AMD processors and system controllers from Texas Instruments and NXP Semiconductors. Implementations support power transitions in laptops and tablets from companies like Apple, Dell, HP, and Asus, enabling suspend, hibernate, runtime power management for PCI Express devices, and system-level policies used in datacenter servers by Hewlett Packard Enterprise and Dell EMC. ACPI also interacts with battery reporting and charging systems used in mobile platforms designed by Samsung and LG Electronics.

Configuration and Embedded Controller

ACPI mediates hardware configuration through firmware tables authored by OEM firmware teams at Dell Inc., HP, Lenovo, and Acer Inc., and often relies on an embedded controller (EC) microcontroller family produced by vendors like Nuvoton Technology, STMicroelectronics, and Atmel. The EC executes platform-specific handlers for events such as lid switches, keyboard backlight, and thermal throttling in notebooks from Sony, Toshiba, and Microsoft Surface. ACPI methods can invoke EC commands and GPIO controllers standardized in specifications influenced by Intel and ARM reference designs. Platform firmware tools from projects like Coreboot and proprietary BIOS/UEFI implementations by Phoenix Technologies and American Megatrends author and expose ACPI tables for operating systems and hypervisors.

Operating System Integration

Operating systems implement AML interpreters and ACPI drivers: Microsoft Windows integrates ACPI into its HAL and kernel power manager, while Linux includes the ACPICA reference implementation originating from Intel and maintained in collaboration with distributions such as Red Hat and companies like Canonical. BSD variants—FreeBSD, NetBSD, OpenBSD—and commercial UNIXes such as Oracle Solaris provide ACPI subsystems adapted to their I/O and device models. Virtualization stacks including QEMU, KVM, Xen Project, and VMware ESXi emulate ACPI tables for guest operating systems, and cloud providers such as Amazon Web Services, Microsoft Azure, and Google Cloud Platform rely on hypervisor-mediated ACPI behavior for VM suspend/resume and power state reporting. Mobile OS projects such as Android interact with ACPI on certain x86 tablets and Chromebooks produced by Google and Acer.

Security and Vulnerabilities

ACPI's executable AML and privileged firmware role have produced attack surfaces analyzed by security researchers from institutions like MITRE Corporation, Google Project Zero, Kaspersky Lab, and academic groups at University of California, Berkeley, University of Cambridge, and Technische Universität Darmstadt. Exploits have targeted BIOS/UEFI implementations from American Megatrends, Phoenix Technologies, and OEMs including Dell and Lenovo via malformed ACPI tables or EC commands, prompting advisories from vendors such as Microsoft and Intel. Mitigations include firmware updates from Insyde Software and OEM update tools, enhanced AML verification in projects like ACPICA, and hardening in hypervisors maintained by Red Hat and VMware. Research into secure firmware practices references standards and initiatives by Trusted Computing Group and National Institute of Standards and Technology.

Category:Computer hardware