ACPI

Last updated

Advanced Configuration and Power Interface
AbbreviationACPI
StatusPublished
First publishedDecember 1996
Latest version6.5
August 2022
Organization
Related standards UEFI
Predecessor
Domain Power management firmware
Website uefi.org/acpi

Advanced Configuration and Power Interface (ACPI) is an open standard that operating systems can use to discover and configure computer hardware components, to perform power management (e.g. putting unused hardware components to sleep), auto configuration (e.g. Plug and Play and hot swapping), and status monitoring. It was first released in December 1996. ACPI aims to replace Advanced Power Management (APM), the MultiProcessor Specification, and the Plug and Play BIOS (PnP) Specification. [1] ACPI brings power management under the control of the operating system, as opposed to the previous BIOS-centric system that relied on platform-specific firmware to determine power management and configuration policies. [2] The specification is central to the Operating System-directed configuration and Power Management (OSPM) system. ACPI defines hardware abstraction interfaces between the device's firmware (e.g. BIOS, UEFI), the computer hardware components, and the operating systems. [3] [4]

Contents

Internally, ACPI advertises the available components and their functions to the operating system kernel using instruction lists ("methods") provided through the system firmware (UEFI or BIOS), which the kernel parses. ACPI then executes the desired operations written in ACPI Machine Language (such as the initialization of hardware components) using an embedded minimal virtual machine.

Intel, Microsoft and Toshiba originally developed the standard, while HP, Huawei and Phoenix also participated later. In October 2013, ACPI Special Interest Group (ACPI SIG), the original developers of the ACPI standard, agreed to transfer all assets to the UEFI Forum, in which all future development will take place. [5] The latest version of the standard 6.5 was released in August 2022. [6]

Architecture

The firmware-level ACPI has three main components: the ACPI tables, the ACPI BIOS, and the ACPI registers. The ACPI BIOS generates ACPI tables and loads ACPI tables into main memory. Much of the firmware ACPI functionality is provided in bytecode of ACPI Machine Language (AML), a Turing-complete, domain-specific low-level language, stored in the ACPI tables. [7] To make use of the ACPI 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 bytecode is compiled from the ASL (ACPI Source Language) code. [8] [9]

ACPI Component Architecture (ACPICA)

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. [10] The ACPICA code is used by Linux, Haiku, ArcaOS [11] and FreeBSD, [8] which supplement it with their operating-system specific code.

History

The first revision of the ACPI specification was released in December 1996, supporting 16, 24 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 1999, then Microsoft CEO Bill Gates stated in an e-mail that Linux would benefit from ACPI without them having to do work and suggested to make it Windows-only. [12] [13] [14]

In September 2004, revision 3.0 was released, bringing to the ACPI specification support for SATA interfaces, PCI Express bus, multiprocessor support for more than 256 processors, ambient light sensors and user-presence devices, as well as extending the thermal model beyond the previous processor-centric support.

Released in June 2009, revision 4.0 of the ACPI specification added various new features to the design; most notable are the USB 3.0 support, logical processor idling support, and x2APIC support.

Revision 5.0 of the ACPI specification was released in December 2011, [15] which added the ARM architecture support. The revision 5.1 was released in July 2014. [16]

The latest specification revision is 6.5, which was released in August 2022. [6]

Operating systems

The "It's now safe to turn off your computer" screen in Windows 9x. Most of the computer peripherals are offline, and the only ways to exit this screen are to power off or reset the computer. LOGOS.SYS.png
The "It's now safe to turn off your computer" screen in Windows 9x. Most of the computer peripherals are offline, and the only ways to exit this screen are to power off or reset the computer.
The "It's now safe to turn off your computer" screen in Windows NT 4.0. Unlike Windows 9x and later NT releases, most of the essential computer peripherals are working normally, so the user can opt to restart instead of powering off their computer. Windows NT 4.0 NonACPI Shutdown.png
The "It's now safe to turn off your computer" screen in Windows NT 4.0. Unlike Windows 9x and later NT releases, most of the essential computer peripherals are working normally, so the user can opt to restart instead of powering off their computer.
The "It's now safe to power off the system" screen in Windows 10 and 11. Windows 10 Safe to shutdown screen.png
The "It's now safe to power off the system" screen in Windows 10 and 11.

Microsoft's Windows 98 was the first operating system to implement ACPI, [17] [18] but its implementation was somewhat buggy or incomplete, [19] [20] although some of the problems associated with it were caused by the first-generation ACPI hardware. [21] Other operating systems, including later versions of Windows, macOS, eComStation, ArcaOS, [22] FreeBSD (since FreeBSD 5.0 [23] ), NetBSD (since NetBSD 1.6 [24] ), OpenBSD (since OpenBSD 3.8 [25] ), HP-UX, OpenVMS, Linux, GNU Hurd and PC versions of Solaris, have at least some support for ACPI. [26] Some newer operating systems, like Windows Vista, require the computer to have an ACPI-compliant BIOS, and since Windows 8, the S0ix/Modern Standby state was implemented. [27]

Windows operating systems use acpi.sys [28] to access ACPI events.

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. [29] 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. [30] Similarly, Linux kernel 2.6 may not use ACPI if the BIOS date is before January 1, 2001. [29]

Linux-based operating systems can provide handling of ACPI events via acpid. [31]

OSPM responsibilities

Once an OSPM-compatible operating system activates ACPI, it takes 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

Global states

The ACPI Specification defines the following four global "Gx" states and six sleep "Sx" states for an ACPI-compliant computer system: [32] [33]

GxNameSxDescription
G0WorkingS0The computer is running and the CPU executes instructions. "Awaymode" is a subset of S0, where monitor is off but background tasks are running
G1SleepingS0ix Modern Standby, [34] or "Low Power S0 Idle". Partial processor SoC sleep. [35] [36] Known to ARM and x86 devices.
S1Power on Suspend (POS): Processor caches are flushed, and the CPU(s) stops executing instructions. The power to the CPU(s) and RAM is maintained. Devices that do not indicate they must remain on may be powered off.
S2CPU powered off. Dirty cache is flushed to RAM.
S3Commonly referred to as Standby, Sleep , or Suspend to RAM (STR): RAM remains powered. Fans may turn off. Requires GPU drivers on Windows.
S4 Hibernation or Suspend to Disk: All content of the main memory is saved to non-volatile memory such as a hard drive, and the system is powered down.
G2Soft OffS5
G3Mechanical OffThe computer's power has been totally removed via a mechanical switch (as on the rear of a PSU). The power cord can be removed and the system is safe for disassembly (typically, only the real-time clock continues to run using its own small battery).

The specification also defines a Legacy state: the state of 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

The device states D0–D3 are device dependent:

  • D0 or Fully On is the operating state.
    • As with S0ix, Intel has D0ix states for intermediate levels on the SoC. [37]
  • D1 and D2 are intermediate power-states whose definition varies by device.
  • D3: The D3 state is further divided into D3 Hot (has auxiliary power), and D3 Cold (no power provided):
    • Hot: A device can assert power management requests to transition to higher power states.
    • Cold or Off has the device powered off and unresponsive to its bus.

Processor states

The CPU power states C0–C3 are defined as follows:

Performance state

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. 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. [41]

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.

Interfaces

Hardware

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, [43] 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.

ACPI Platform Error Interface (APEI) is a specification for reporting of hardware errors, e.g. chipset, RAM to the operating system.

Firmware

ACPI defines many tables that provide the interface between an ACPI-compliant operating system and system firmware (BIOS or UEFI). This includes RSDP, RSDT, XSDT, FADT, FACS, DSDT, SSDT, MADT, and MCFG, for example. [44] [45]

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 AML can be decompiled by tools like Intel's iASL (open-source, part of ACPICA) for purposes like patching the tables for expanding OS compatibility. [46] [47]

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

A custom ACPI table called the Windows Platform Binary Table (WPBT) is used by Microsoft to allow vendors to add software into the Windows OS automatically. Some vendors, such as Lenovo, have been caught using this feature to install harmful software such as Superfish. [48] Samsung shipped PCs with Windows Update disabled. [48] Windows versions older than Windows 7 do not support this feature, but alternative techniques can be used. This behavior has been compared to rootkits. [49] [50]

Tables

PHAT
Platform Health Assessment Table
SLIP
Software Licensing Description Table

Criticism

Ubuntu founder Mark Shuttleworth says ACPI is a security risk. [51] He says "arguing for ACPI on your next-generation device is arguing for a trojan horse of monumental proportions to be installed in your living room and in your data centre" and "firmware on your device is the NSA's best friend". He goes on to say, "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." He suggests open-source, declarative firmware (ACPI or non-ACPI) as a solution. [52]

Overall design decision was not without criticism. In November 2003, Linus Torvalds—author of the Linux kernel—described ACPI as "a complete design disaster in every way". [52] [53]

See also

Further reading

Related Research Articles

<span class="mw-page-title-main">BIOS</span> Firmware for hardware initialization and OS runtime services

In computing, BIOS is firmware used to provide runtime services for operating systems and programs and to perform hardware initialization during the booting process. The BIOS firmware comes pre-installed on an IBM PC or IBM PC compatible's system board and exists in some UEFI-based systems to maintain compatibility with operating systems that do not support UEFI native operation. The name originates from the Basic Input/Output System used in the CP/M operating system in 1975. The BIOS originally proprietary to the IBM PC has been reverse engineered by some companies looking to create compatible systems. The interface of that original system serves as a de facto standard.

<span class="mw-page-title-main">Open Firmware</span> Standard for computer bootstrap code

Open Firmware is a standard defining the interfaces of a computer firmware system, formerly endorsed by the Institute of Electrical and Electronics Engineers (IEEE). It originated at Sun Microsystems where it was known as OpenBoot, and has been used by multiple vendors including Sun, Apple, IBM and ARM.

Hardware abstractions are sets of routines in software that provide programs with access to hardware resources through programming interfaces. The programming interface allows all devices in a particular class C of hardware devices to be accessed through identical interfaces even though C may contain different subclasses of devices that each provide a different hardware interface.

<span class="mw-page-title-main">UEFI</span> Operating system and firmware specification

Unified Extensible Firmware Interface is a specification that defines the architecture of the platform firmware used for booting the computer hardware and its interface for interaction with the operating system. Examples of firmware that implement the specification are AMI Aptio, Phoenix SecureCore, TianoCore EDK II, InsydeH2O. UEFI replaces the BIOS which was present in the boot ROM of all personal computers that are IBM PC compatible, although it can provide backwards compatibility with the BIOS using CSM booting. Intel developed the original Extensible Firmware Interface (EFI) specification. Some of the EFI's practices and data formats mirror those of Microsoft Windows. In 2005, UEFI deprecated EFI 1.10.

<span class="mw-page-title-main">American Megatrends</span> International hardware and software company

American Megatrends International, LLC, doing business as AMI, is an international hardware and software company, specializing in PC hardware and firmware. The company was founded in 1985 by Pat Sarma and Subramonian Shankar. It is headquartered in Building 800 at 3095 Satellite Boulevard in unincorporated Gwinnett County, Georgia, United States, near the city of Duluth, and in the Atlanta metropolitan area.

<span class="mw-page-title-main">QEMU</span> Free virtualization and emulation software

QEMU is a free and open-source emulator. It emulates a computer's processor through dynamic binary translation and provides a set of different hardware and device models for the machine, enabling it to run a variety of guest operating systems. It can interoperate with Kernel-based Virtual Machine (KVM) to run virtual machines at near-native speed. QEMU can also do emulation for user-level processes, allowing applications compiled for one architecture to run on another.

In computing, the System Management BIOS (SMBIOS) specification defines data structures that can be used to read management information produced by the BIOS of a computer. This eliminates the need for the operating system to probe hardware directly to discover what devices are present in the computer. The SMBIOS specification is produced by the Distributed Management Task Force (DMTF), a non-profit standards development organization. The DMTF estimates that two billion client and server systems implement SMBIOS.

<span class="mw-page-title-main">UEFI Forum</span> Non-profit corporation based in Oregon

UEFI Forum, Inc. is an alliance between technology companies to coordinate the development of the UEFI specifications. The board of directors includes representatives from twelve promoter companies: AMD, American Megatrends, ARM, Apple, Dell, Hewlett Packard Enterprise, HP Inc., Insyde Software, Intel, Lenovo, Microsoft, and Phoenix Technologies.

The High Precision Event Timer (HPET) is a hardware timer available in modern x86-compatible personal computers. Compared to older types of timers available in the x86 architecture, HPET allows more efficient processing of highly timing-sensitive applications, such as multimedia playback and OS task switching. It was developed jointly by Intel and Microsoft and has been incorporated in PC chipsets since 2005. Formerly referred to by Intel as a Multimedia Timer, the term HPET was selected to avoid confusion with the software multimedia timers introduced in the MultiMedia Extensions to Windows 3.0.

<span class="mw-page-title-main">GUID Partition Table</span> Computer disk partitioning standard

The GUID Partition Table (GPT) is a standard for the layout of partition tables of a physical computer storage device, such as a hard disk drive or solid-state drive, using universally unique identifiers (UUIDs), which are also known as globally unique identifiers (GUIDs). Forming a part of the Unified Extensible Firmware Interface (UEFI) standard, it is nevertheless also used for some BIOSs, because of the limitations of master boot record (MBR) partition tables, which use 32 bits for logical block addressing (LBA) of traditional 512-byte disk sectors.

System Management Mode is an operating mode of x86 central processor units (CPUs) in which all normal execution, including the operating system, is suspended. An alternate software system which usually resides in the computer's firmware, or a hardware-assisted debugger, is then executed with high privileges.

<span class="mw-page-title-main">Apple–Intel architecture</span> Unofficial name used for Macintosh models that use Intel x86 processors

The Apple–Intel architecture, or Mactel, is an unofficial name used for Macintosh personal computers developed and manufactured by Apple Inc. that use Intel x86 processors, rather than the PowerPC and Motorola 68000 ("68k") series processors used in their predecessors or the ARM-based Apple silicon SoCs used in their successors. As Apple changed the architecture of its products, they changed the firmware from the Open Firmware used on PowerPC-based Macs to the Intel-designed Extensible Firmware Interface (EFI). With the change in processor architecture to x86, Macs gained the ability to boot into x86-native operating systems, while Intel VT-x brought near-native virtualization with macOS as the host OS.

<span class="mw-page-title-main">EFI system partition</span> Partition used by Unified Extensible Firmware Interface

The EFIsystem partition or ESP is a partition on a data storage device that is used by computers that have the Unified Extensible Firmware Interface (UEFI). When a computer is booted, UEFI firmware loads files stored on the ESP to start operating systems and various utilities.

In the context of free and open-source software, proprietary software only available as a binary executable is referred to as a blob or binary blob. The term usually refers to a device driver module loaded into the kernel of an open-source operating system, and is sometimes also applied to code running outside the kernel, such as system firmware images, microcode updates, or userland programs. The term blob was first used in database management systems to describe a collection of binary data stored as a single entity.

<span class="mw-page-title-main">Legacy Plug and Play</span> Series of specifications and Microsoft Windows features

The term Legacy Plug and Play, also shortened to Legacy PnP, describes a series of specifications and Microsoft Windows features geared towards operating system configuration of devices, and some device IDs are assigned by UEFI Forum. The standards were primarily aimed at the IBM PC standard bus, later dubbed Industry Standard Architecture (ISA). Related specifications are also defined for the common external or specialist buses commonly attached via ISA at the time of development, including RS-232 and parallel port devices.

The Linux booting process involves multiple stages and is in many ways similar to the BSD and other Unix-style boot processes, from which it derives. Although the Linux booting process depends very much on the computer architecture, those architectures share similar stages and software components, including system startup, bootloader execution, loading and startup of a Linux kernel image, and execution of various startup scripts and daemons. Those are grouped into 4 steps: system startup, bootloader stage, kernel stage, and init process. When a Linux system is powered up or reset, its processor will execute a specific firmware/program for system initialization, such as Power-on self-test, invoking the reset vector to start a program at a known address in flash/ROM, then load the bootloader into RAM for later execution. In personal computer (PC), not only limited to Linux-distro PC, this firmware/program is called BIOS, which is stored in the mainboard. In embedded Linux system, this firmware/program is called boot ROM. After being loaded into RAM, bootloader will execute to load the second-stage bootloader. The second-stage bootloader will load the kernel image into memory, decompress and initialize it then pass control to this kernel image. Second-stage bootloader also performs several operation on the system such as system hardware check, mounting the root device, loading the necessary kernel modules, etc. Finally, the very first user-space process starts, and other high-level system initializations are performed.

The MultiProcessor Specification (MPS) for the x86 architecture is an open standard describing enhancements to both operating systems and firmware, which will allow them to work with x86-compatible processors in a multi-processor configuration. MPS covers Advanced Programmable Interrupt Controller (APIC) architectures.

Simple Firmware Interface (SFI) is developed by Intel Corporation as a lightweight method for firmware to export static tables to the operating system. It is supported by Intel's hand-held Moorestown platform.

<span class="mw-page-title-main">SeaBIOS</span> Open-source implementation of x86 BIOS

SeaBIOS is an open-source implementation of an x86 BIOS, serving as a freely available firmware for x86 systems. Aiming for compatibility, it supports standard BIOS features and calling interfaces that are implemented by a typical proprietary x86 BIOS. SeaBIOS can either run on bare hardware as a coreboot payload, or can be used directly in emulators such as QEMU and Bochs.

InstantGo, also known as InstantOn or Modern Standby, is a Microsoft specification for Windows 8 hardware and software that aims to bring smartphone-type power management capabilities to the PC platform, as well as increasing physical security.

References

  1. ↑ "ACPI Overview" (PDF). www.acpi.info. Archived from the original (slide show in PDF) on May 25, 2019.
  2. ↑ "APM BIOS Specification". Intel Corporation, Microsoft Corporation. February 1996. Archived from the original (RTF) on February 6, 2012. Retrieved July 2, 2010.
  3. ↑ "What is ACPI (Advanced Configuration and Power Interface)? - Definition from WhatIs.com". SearchWindowsServer. Retrieved September 18, 2020.
  4. ↑ "ACPI Device Tree - Representation of ACPI Namespace — The Linux Kernel documentation". www.kernel.org. Retrieved September 18, 2020.
  5. ↑ "The Advanced Configuration & Power Interface web page has a prominent note that links to the Preexisting ACPI Specifications page on the UEFI web site". acpi.org. July 23, 2014. Archived from the original on June 22, 2011. Retrieved January 25, 2016.
  6. 1 2 "Advanced Configuration and Power Interface Specification, Release 6.5" (PDF). UEFI.org/specifications. August 2022. Retrieved October 4, 2022.
  7. ↑ Bernhard Kauer (August 2009). "ATARE: ACPI Tables and Regular Expressions" (PDF). Retrieved February 18, 2019.
  8. 1 2 ACPI implementation on FreeBSD - Usenix
  9. ↑ ACPI in Linux, 2005
  10. ↑ ACPICA: ACPI Component Architecture
  11. ↑ "Readme for the ACPI Driver Package". arcanoae.com. Retrieved September 6, 2020.
  12. ↑ "Microsoft wollte ACPI nur für Windows". Der Standard (in Austrian German). Retrieved November 6, 2022.
  13. ↑ "Microsoft: ACPI sollte nur unter Windows funktionieren". Golem.de . Retrieved November 6, 2022.
  14. ↑ Gates, Bill (January 24, 1999). "ACPI extensions" (PDF). Archived from the original (PDF) on February 2, 2007.
  15. ↑ Hewlett-Packard; Intel Corporation; Microsoft; Phoenix Technologies; Toshiba (December 6, 2011). "Advanced Configuration and Power Interface Specification (Revision 5.0)" (PDF). acpi.info. Archived from the original (PDF) on September 14, 2012. Retrieved November 17, 2013.
  16. ↑ "Advanced Configuration and Power Interface Specification (Revision 5.1)" (PDF). uefi.org. July 23, 2014. Retrieved May 24, 2015.
  17. ↑ "Limitations When Using Microsoft Windows 98 on Compaq Armada Portables" (PDF). physik.hu-berlin.de. October 1998. p. 3. Retrieved January 27, 2014.[ permanent dead link ]
  18. ↑ "Windows 98 on ThinkPad systems - ThinkPad General". Support.lenovo.com. Archived from the original on February 3, 2014. Retrieved January 27, 2014.
  19. ↑ Robert Cowart; Brian Knittel (2000). Using Microsoft Windows 2000 Professional . Que Publishing. p.  30. ISBN   978-0-7897-2125-9.
  20. ↑ Windows 98 Does Not Support ACPI Passive Cooling Mode
  21. ↑ "Cover Story: Win98 Bugs & Fixes - December 1998". winmag.com. Archived from the original on October 13, 1999.
  22. ↑ "ArcaOS Changelog" . Retrieved August 24, 2020.
  23. ↑ "FreeBSD 5.0-RELEASE Announcement". www.freebsd.org. Retrieved December 3, 2020.
  24. ↑ "acpi(4) - NetBSD Manual Pages". man.netbsd.org. Retrieved December 3, 2020.
  25. ↑ "acpi(4) - OpenBSD manual pages". man.openbsd.org. Retrieved December 3, 2020.
  26. ↑ Therien, Guy (January 6, 2000). "ACPI 2.0 Specification Technical Review, Intel Developer Forum" (PPT). Intel Corporation. Archived from the original on July 21, 2011. Retrieved August 21, 2011.
  27. ↑ Marshall, Allen. "ACPI in Windows Vista" (PPT). Microsoft Corporation . Retrieved July 2, 2010.
  28. ↑ "Acpi.sys: The Windows ACPI Driver". Microsoft Corporation. June 15, 2017. Retrieved September 20, 2019.
  29. 1 2 The State of ACPI in the Linux Kernel
  30. ↑ ACPI BIOS. msdn.microsoft.com.
  31. ↑ Linux in a nutshell. Ellen Siever, Ellen Siever (5th ed.). Beijing: O'Reilly. 2005. p. 36. ISBN   978-0-596-52949-9. OCLC   773210086.{{cite book}}: CS1 maint: others (link)
  32. ↑ ACPI Spec Rev 5.0 - dated December 6, 2011
  33. ↑ Anand Lal Shimpi (October 5, 2012). "Intel's Haswell Architecture Analyzed". AnandTech . Retrieved October 20, 2013.
  34. ↑ windows-driver-content. "Modern Standby". docs.microsoft.com. Retrieved March 20, 2020.
  35. ↑ "S0ix States". software.intel.com. March 9, 2020.
  36. ↑ Wang, Wendy (October 17, 2018). "How to achieve S0ix states in Linux*". 01.org.
  37. ↑ "D0ix States". software.intel.com. March 9, 2020.
  38. ↑ "Athlon II X2: Hardware C1E and Return of the CnQ Bug". AnandTech . Retrieved October 26, 2020.
  39. ↑ Wasson, Scott (February 21, 2005). "Intel's Pentium 4 600 series processors". The Tech Report. p. 2.
  40. ↑ "Processor Package and Core C-States". AnandTech. June 9, 2013. Retrieved October 20, 2013.
  41. ↑ "Advanced Configuration and Power Interface Specification, Revision 3.0, Section 2.6 Device and Processor Performance State Definitions" (PDF). ACPI.info. September 2, 2004. p. 23. Archived from the original (PDF) on November 28, 2015. Retrieved August 19, 2015.
  42. ↑ Link aggregation
  43. ↑ Intel Corporation (September 2006). "Intel Processor Vendor-Specific ACPI" (PDF). Archived from the original (PDF) on December 25, 2012. Retrieved October 5, 2014.
  44. ↑ Brown, Len (July 20, 2005). "ACPI in Linux". Ottawa Linux Symposium: 3. CiteSeerX   10.1.1.173.2206 .
  45. ↑ "ACPI Tables — The Linux Kernel documentation". www.kernel.org. Archived from the original on October 20, 2020. Retrieved November 8, 2020.
  46. ↑ "DSDT". ArchWiki.
  47. ↑ "Getting Started With ACPI". GitBook.
  48. 1 2 Hoffman, Chris (August 19, 2015). "Zombie Crapware: How the Windows Platform Binary Table Works". How-To Geek.
  49. ↑ "Vendors 'rootkit': 'Windows Platform Binary Table' (WPBT)". Born's Tech and Windows World. December 6, 2017.
  50. ↑ Mayank Sharma (September 27, 2021). "Millions of Windows 10 PCs exposed by nasty security vulnerability". TechRadar . Retrieved November 10, 2022.
  51. ↑ Mark Shuttleworth blog (March 17, 2014), "ACPI, firmware and your security"
  52. 1 2 Linux Magazine issue 162, May 2014, page 9
  53. ↑ Searls, Doc (November 25, 2003). "Linus & the Lunatics, Part II". Linux Journal. Retrieved January 13, 2010.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.