{{Copyedit|date=June 2008}}
The '''Advanced Configuration and Power Interface''' ('''ACPI''') specification, an [[Open standard|open industry standard]] first released in December 1996 (developed by [[Hewlett-Packard|HP]], [[Intel]], [[Microsoft]], [[Phoenix Technologies|Phoenix]], [[Toshiba]], and [[Dell]]), defines common interfaces for hardware recognition, motherboard and device configuration and [[power management]]. According to its specification,[http://www.acpi.info/spec.htm ACPI] "ACPI is the key element in Operating System-directed configuration and Power Management (OSPM)."
The [[as of 2008| latest]] revision of the ACPI specification, 3.0b, appeared on October 10, 2006.
== Overview ==
== 概要 ==
The most widely recognized element of the standard, power management has seen a major improvement.
作为[[标准]]中最广为认可的部分，[[电源管理]]经历了较多的改进。
Previously, the [[Advanced Power Management]] model (APM) assigned power management control almost exclusively to the [[BIOS]], which greatly limited the functionality of the OS in controlling power consumption.
早先，[[Advanced Power Management]]模型([[APM]])将电源管理几乎完全分配给[[BIOS]]控制，这大大的限制了[[操作系统]]在控制电能消耗方面的功能。
Currently, ACPI brings power management features previously only available in portable computers (such as laptops) to Desktops, Workstations and Servers. For example, systems may be put into extremely low power consumption states. These are the "sleep" and "hibernate" settings available on most Desktops. The Sleep and Hibernate states can wake the system by moving the mouse, pressing a key on the keyboard, receiving a message from another computer (if connected to a LAN) or critical system errors.
当前，[[ACPI]]的电源管理特性以前只适用从便携式计算机（例如[[膝上型计算机]]）到[[桌上型电脑]]、[[工作站]]和[[服务器]]。例如，系统可能会进入极低功率消耗状态。这些就是可利用在多数桌面型电脑上的“睡眠”和“休眠”设置。睡眠和休眠状态可以通过移动鼠标，按键盘按键，从另外一台电脑接收一条信息（如果连接到了一个[[局域网]]）或者重大系统错误来唤醒系统。
Some vendors such as ASUS and Compaq have provided other special keys to bring the system back to full functionality.{{Clarifyme|date=September 2008}}
Now if ACPI is implemented in the BIOS and other system hardware, it may be invoked (triggered) by the operating system.
现在，如果[[ACPI]]在[[BIOS]]和其他系统硬件中被实现，它就可以由操作系统所调用(触发)。
ACPI可以实现的功能包括：
*系统电源管理（System power management）
*设备电源管理（Device power management）
*处理器电源管理（Processor power management）
*设备和处理器性能管理（Device and processor performance management）
*配置/即插即用（Configuration/Plug and Play）
*系统事件（System Event）
*电池管理（Battery management）
*温度管理（Thermal management）
*嵌入式控制器（Embedded Controller）
*SMBus控制器（SMBus Controller）
Windows 98 was the first Microsoft OS to support ACPI. FreeBSD v5.0 was the first UNIX OS to support ACPI{{Fact|date=August 2008}}. Linux, NetBSD and OpenBSD all have at least some support for ACPI.
Windows 98是支持ACPI的第一个微软的[[操作系统]]。FreeBSD v5.0是支持ACPI的第一个UNIX操作系统 {{Fact|time=August 2008}}。Linux、NetBSD和OpenBSD都至少有一些支持ACPI。
== States ==
== 状态 ==
=== Global states ===
=== 全局状态（Global System States） ===
The ACPI specification defines the following seven states (so-called global states) which an ACPI-compliant computer system can be in:
[[ACPI]]规范定义了一台兼容ACPI的[[计算机]]系统可以有以下七个状态（所谓的全局状态）：
* '''G0''' ('''S0''') ''Working'': the normal working state of the computer — the operating system and applications are running. The [[CPU]](s) execute instructions. Within this state (i.e., without entering G1 ''Sleeping''), it is possible for [[CPU]](s) and devices like [[hard drive]]s, [[DVD drive]]s, etc. to be repeatedly put into and come back from low-energy states, called [[#Processor states|''C0''–''C''n]] and [[#Device states|''D0''–''D3'']]. ([[Laptop]]s, for example, routinely power down all currently unused devices when running on battery; some [[desktop computer|desktops]] also do this to reduce noise.)
*'''G0''('''S0''')''正常工作状态''：计算机的正常工作状态-操作系统和应用程序都在运行。[[CPU]](s)执行指令。 在这个状态下(即没有进入G1''睡眠'')，[[CPU]]和像硬盘、DVD驱动器等等这些的设备可以一再的进入和从低能源状态回来，叫做[[#处理器状态|''C0''-''C''n]]和[[#设备状态|''D0''-''D3'']]。(例如[[膝上型计算机]]，当使用电池运行的时候通常关掉所有当前未使用的设备；一些[[桌上型计算机]]也这么做来减少噪声。)
* '''G1''' ''Sleeping'' subdivides into the four states S1 through S4. The time needed to bring the system from here back into G0 ''Working'' (''wake-latency'' time) is shortest for S1, short for S2 and S3, and not so short for S4.
*'''G1''' ''睡眠'' 细分为从S1到S4这四种状态。系统从这几种状态被唤醒到G0''运行''（''[[唤醒等待]]''时间）所需的时间最短的是S1，较短的是S2和S3，不太短的是S4。
** '''S1''': the most power-hungry of sleep-modes. All processor caches are flushed, and the CPU(s) stop executing instructions. Power to the CPU(s) and RAM is maintained; devices that do not indicate they must remain on may be powered down. This mode is often referred to as ''Power On Standby'' or simply POS, particularly in BIOS configuration screens. Some newer machines do not support S1; older machines are more likely to support S1 than S3.
**'''S1'''：最耗电的睡眠模式。处理器的所有[[寄存器]]被刷新，并且[[CPU]]停止执行指令。[[CPU]]和[[内存]]的电源一直维持着，一些设备如果没有被使用那么就会被停止供电。这种模式通常指''上电待机''或者简单叫做[[POS]]，特别在[[BIOS]]设置界面上。一些新式的计算机不再支持S1；老式的电脑对S1支持肯能要比S3好。
** '''S2''': a deeper sleep-state than S1, where the CPU is powered off; however, it is not commonly implemented.
**'''S2'''：一个比S1更深的睡眠状态，不过已经不给[[CPU]]供电了；然而，通常这种模式并不被采用。
** '''S3''': known as ''Suspend to RAM'' (STR) in the BIOS, ''Standby'' in versions of [[Microsoft Windows|Windows]] through [[Windows XP]] and in some varieties of [[Linux]], ''Sleep'' in [[Windows Vista]] and [[Mac OS X]], although the ACPI specification mentions only the terms ''S3'' and ''Sleep''. In this state, main memory ([[RAM]]) is still powered, although it is almost the only component that is. Since the state of the [[operating system]] and all applications, open documents, etc. lies all in main memory, the user can resume work exactly where they left off—the main memory content when the computer comes back from S3 is the same as when it was put into S3. (The specification mentions that S3 is rather similar to S2, only that some more components are powered down in S3.) S3 has two advantages over S4; the computer is faster to resume than to reboot, secondly if any running applications (opened documents, etc) have private information in them, this will not be written to the disk. However, [[Caching#Disk buffer|disk caches]] may be flushed to prevent data corruption in case the system doesn't wake up e.g. due to power failure.
**''' S3 '''：在BIOS中叫做"挂起到[[内存]]" (Suspend to RAM/STR)，在[[Windows XP]]以后的[[Microsoft Windows|Windows]]版本和一些[[Linux]]发行版中叫做"[[待机]](Standby)"， 在[[Windows Vista]]和[[Mac OS X]]则叫做"睡眠(Sleep)"，虽然ACPI规范仅仅提到术语"S3"和"睡眠(Sleep)"。在这个状态下，主存储器([[RAM]])仍然有电源供给，尽管它也是几乎唯一的有电源供给的原件。因为[[操作系统]]、所有应用程序和被打开的文档等等的状态都是保存在主存储器中，用户可以把工作恢复到正好上次他们保持的状态-计算机从S3状态回来时主存储器的内容和它进入S3状态时候的内容是相同象的。(规范中提到了S3和S2是相当类似的，只有更多的元件在S3状态下会被关掉电源。) 相比较S4来说S3有两个好处；计算机恢复的过程比重启要快，第二，如果任何正在运行的应用程序(被打开的文档等等)有私有信息在里面，这些信息是不会被写到硬盘上的。然而，在系统不能被唤醒比如遇到了电源故障的时候， [[高速缓存#.E6.A6.82.E5.BF.B5.E7.9A.84.E6.89.A9.E5.85.85|高速缓冲存储器]]可能会被flushed来防止数据毁坏。
** '''S4''': ''Hibernation'' in [[Microsoft Windows|Windows]], ''Safe Sleep'' in [[Mac OS X]], also known as ''Suspend to disk'', although the ACPI specification mentions only the term ''S4'' (''main article: [[Hibernate (OS feature)]]''). In this state, all content of [[RAM|main memory]] is saved to non-volatile memory such as a [[hard drive]], preserving the state of the operating system, all applications, open documents etc. That means that after coming back from S4, the user can resume work where it was left off in much the same way as with S3. The difference between S4 and S3, apart from the added time of moving the main memory content to disk and back, is that a power loss of a computer in S3 makes it lose all data in main memory, including all unsaved documents, while a computer in S4 is unaffected. S4 is quite different from the other ''S'' states and actually resembles G2 ''Soft Off'' and G3 ''Mechanical Off'' more than it resembles S1–S3. A system that's in S4 can also be put in G3 (''Mechanical Off'') and still keep its S4 save state information, so that it can resume the operating state after getting back power.
**'''S4'''： 在[[微软|Windows]]中叫''休眠''， 在[[Mac OS X]]中叫作''安全睡眠''，也称为''挂起到硬盘''，虽然ACPI规范中只提到了一个术语''S4''（''main article:[[Hibernate(OS feature)]]'')。在这个状态下，所有[[内存|主存储器]]的内容被储存在非挥发性存储器，例如[[硬盘]]，保护操作系统当前的状态，包括所有应用程序,打开的文档等.这意味着从S4恢复后，用户可以恢复到原本的工作状态，采用的方法和S3是一样的。S4和S3之间的差异是，除了把主存储器中的内容移进移出所消耗的时间以外,在S3状态下的时候如果一旦停电了,所有主存储器上的数据就会丢失,包括所有的没有保存的文档,而在S4状态下则没有影响.S4和其他的''S''状态有很大不同,事实上更类似G2''Soft Off''状态和G3 ''Mechanical Off''状态,而不是S1-S3.在S4状态下的系统同样可进入G3(''Mechanical Off'')状态,并且保留S4时候的状态信息.所以它可以恢复到以前的运行状态在关掉电源之后.
* '''G2''' ('''S5''') ''Soft Off''-- ''G2'', ''S5'', and ''Soft Off'' are [[synonym]]s. G2 is almost the same as G3 ''Mechanical Off'', but some components remain powered so the computer can "wake" from input from the keyboard, clock, [[Wake-on-Ring| modem]], [[Wake on LAN|LAN]], or [[Universal Serial Bus|USB]] device.[http://www.kananov.com/notes/s3 Aram Kananov » How To: ACPI Suspend to RAM on Dell Latitude D800 with Fedora Core 3] This state equates to G3 ''Mechanical Off'' in that the [[Booting|boot procedure]] must be run to bring the system from G2 to G0 ''Working''. G3 ''Mechanical Off'' is entered only when a power loss occurs, whereas G2 is initiated by the [[operating system]] (typically because the user issued a shutdown command in some way). The computer is not safe for disassembly in the G2 state due to the components that remain powered. It is advisable to unplug a [[desktop computer]] and wait 20 seconds prior to disassembly; although internal drives are usually not powered, the ([[PS/2 connector|PS2]]) keyboard, USB ports, [[mainboard]], [[expansion card]]s, and [[Computer power supply|power supply]] may remain powered, even if the computer is not used to wake from input to these devices.
* '''G2'''（'''S5'''）''Soft Off''--''G2''，''S5''，和''Soft Off''都是相同的叫法。G2和G3''Mechanical Off''几乎是相同的，但有些部件仍然带电，使计算机仍然可以被键盘、时钟、[[Wake-on-Ring|modem]]（电话唤醒）、[[Wake on LAN|LAN]]（网络唤醒）还有[[Universal Serial Bus|USB]]设备所唤醒。[http://www.kananov.com/notes/s3 Aram Kananov » How To: ACPI Suspend to RAM on Dell Latitude D800 with Fedora Core 3]在启动系统从G2恢复到G0''正常工作''模式的过程中，无论是G3 ''Mechanical Off''还是G2都得运行[[启动程式]]来启动操作系统。
* '''G3''' ''Mechanical Off'': The computer's power consumption approaches close to zero, to the point that the power cord can be removed and the system is safe for disassembly (typically, only the [[real-time clock]] is running off its own small battery). The computer falls into this state when a power loss occurs, e.g. in case of a power outage. Once power is restored, a full [[Booting|boot procedure]] is necessary to bring the system from G3 to G0 ''Working''.
Furthermore, a state ''Legacy'' is defined as the state when an operating system runs which does not support ACPI. In this state, the hardware and power are not managed via ACPI, effectively disabling ACPI.
此外，当操作系统在不支持ACPI的情况下运行，这种状态被定义为''Legacy''。在这个状态下，硬件和电源不是通过ACPI来管理的，实际上已经禁用了ACPI。
(Reference: ACPI specification 3.0b is linked to under [[#External links|External links]], section 7.3.4)
（参考资料：ACPI规范3.0b版的链接在下面 [[#External links|External links]], 查看chapter 7.3.4)
=== Device states ===
===设备电源状态(Device Power State)===
设备状态对于用户来说往往是不可见的，比如当一个设备已经没有电源供应的时候，可能整个系统还是在工作状态，[[光驱]]应该是一个很好的例子吧。
设备状态是与设备相关的状态，他们的定义和以下四个因素有关：
'''电源消耗'''（Power consumption），设备用电量的多少。
'''设备状态/环境'''（Device context），设备（从D0进入其他状态的时候）保留了多少原来的状态/环境。操作系统负责保存丢失的设备状态/环境。
'''设备驱动'''（Device driver），让设备恢复到D0，[[驱动程序]]应该做什么（或者做多少）。
The device states ''D0''-''D3'' are device-dependent:
设备状态有一下几个：
* D0 ''Fully-On'' is the operating state.
* D0 ''Fully-On'' 是（正常）[[工作]]状态，[[电源]]消耗量最多，设备是完全被相应的，并且设备保留了全部的设备状态/环境。
* D1 and D2 are intermediate power-states whose definition varies by device.
* D1 和 D2是中间电源状态，它的定义根据设备的不同而有所不同。
* D3 ''Off'' has the device powered off and unresponsive to its bus.
* D3 ''Off''是设备电源关闭所以对总线来说是没有相应的。设备状态/[[环境]]全部丢失，[[操作系统]]会重新初始化设备当重新给它加电的时候。这个状态下的设备恢复到D0相比之下需要最长的时间。
{| class="wikitable" style="width:700px;"
|+ '''设备状态总结'''
|-
! 设备状态 || 电源消耗 || 保留设备状态信息 || 驱动程序恢复
|-
|| D1 || D0>D1>D2>D3 || >D2 ||
|| D2 || D0>D1>D2>D3 ||
|-
|| D3 - Off || 0 || 没有保留 || 完全[[初始化]]并且装载
|}
=== Processor states ===
===处理器电源状态(Processor Power State)===
处理器电源状态（C0到C3状态，后面还有Gn）是指在G0状态下（只对G0状态有效，在其他状态下不予讨论）的处理器电能消耗和温度管理的状态。
只有C0状态下CPU才会执行指令，C1到Cn状态下CPU都处于各种不同程度的睡眠状态（''Sleeping States''），在这睡眠状态下，CPU都有一个恢复到C0的[[唤醒时间]]（''latency''），它是和CPU的电能消耗有关的，通常，用电能量越小意味着得花更长的时间恢复到C0状态，也就是唤醒时间越长。
当在C0状态下时，ACPI允许通过定义节流阀（''throttling''）过程，和通过进去多性能状态（multiple performance states，P-states）来改变处理器的性能。
The CPU power states ''C0''-''C3'' are defined as follows:
各个状态的定义如下所示：
* C0 is the operating state.
* C0是正常工作状态，当[[处理器]]处于这种状态下的时候，它能正常处理[[指令]]。
* C1 (often known as ''Halt'') is a state where the processor is not executing instructions, but can return to an executing state essentially instantaneously. Some processors, such as the [[Pentium 4]], also support an Enhanced C1 state (C1E) for lower power consumption.
* C1（通常称为''Halt''）拥有最短的唤醒时间，这个延时必须短到操作系统软件使用CPU的时候不会考虑到唤醒时间方面的因素。一些处理器，比如说[[奔腾4]]（[[Pentium 4]]），支持[[C1E]]（Enhanced C1 state）这样的低电能消耗技术。
这个状态是不被软件所见的。
* C2 (often known as ''Stop-Clock'') is a state where the processor maintains all software-visible state, but may take longer to wake up.
* C2 (通常称为''Stop-Clock'')，这个状态下[[处理器]]维持着所有的软件所见的状态信息，但是需要更长的时间来恢复到C0。这个状态下情况最坏的硬件唤醒时间是由ACPI固件提供，并且[[操作系统]]软件可以利用这些信息来决定是采用C1而不是C2状态，C2比C1更省电。
* C3 (often known as ''Sleep'') is a state where the processor does not need to keep its [[cache]] coherent, but maintains other state. Some processors have variations on the C3 state (Deep Sleep, Deeper Sleep, etc.) that differ in how long it takes to wake the processor.
* C3 (通常称为''Sleep'')，相比C1和C2更省电了。这个状态下情况最坏的硬件唤醒时间是由ACPI固件提供，并且操作系统软件可以利用这些信息来决定是采用C2而不是C3状态，当处于C3状态时，处理器[[缓存]]保留了所有的状态信息，但是忽略所有的[[侦听]]。操作系统软件负责保证缓存数据的一致性。
=== Performance states ===
===设备和处理器性能状态（Device and Processor Performance States）===
While a device or processor operates (D0 and C0, respectively), it can be in one of several [[Voltage and frequency scaling|power-performance states]]. These states are implementation-dependent, but P0 is always the highest-performance state, with P1 to P''n'' being successively lower-performance states, up to an implementation-specific limit of ''n'' no greater than 16.
设备和处理器性能状态（Px状态）是在C0（对于处理器）和D0（对于设备）下定义的电源消耗和能力的状态。性能状态允许[[OSPM]]在性能和能源消耗之间取得平衡。P0是坐高性能状态，从P1到P''n''是连续的低性能状态，最高限制''n''为16。
* P0状态，使用最大性能并且消耗的电能最多。
* P1状态，性能比前者要小，但是消耗电能也相应少一些。
* Pn状态，n是的大小是依赖于处理器和设备的，处理器和设备可以定一个任意的不超过16的数字。
P-states have become known as [[SpeedStep]] in [[Intel]] processors, [[PowerNow!]] or [[Cool'n'Quiet]] in [[Advanced Micro Devices|AMD]] processors and [[PowerSaver]] in [[VIA]] processors.
这个状态在Intel处理器中称为[[SpeedStep]]，在[[Advanced Micro Devices|AMD]]处理器中称为[[PowerNow!]]或[[Cool'n'Quiet]]，在[[VIA]]处理器中称为[[PowerSaver]]。
== ACPI Tables ==
{{Wikify|date=September 2008}}
Operating-systems use these tables to get information about hardware.
;RSDP (Root System Description Pointer)
;RSDT (Root System Description Table)
;DSDT (Differentiated System Description Table)
It is a part of the ACPI specification and it supplies configuration information about a base system.
The DSDT comprises a system description table header, followed by a definition block. The definition block is encoded using ACPI Machine Language (AML), and unlike other definition blocks on the system, the DSDT definition block can not be unloaded, as it provides the basic ACPI namespace scope that all other dynamic definition blocks can later add onto.
;XSDT (Extended System Description Table)
;FADT (Fixed ACPI Description Table)
;FACS (Firmware ACPI Control Structure)
;SBST (Smart Battery Table)
;ECDT (Embedded Controller Boot Resources Table)
;MADT (Multiple APIC Description Table)
Different [[Advanced Programmable Interrupt Controller|APIC]] models exist. This table is used to identify the model and provide the starting point (pointers to other tables/structures) that implements it.
;SRAT (System Resource Affinity Table)
Operating-systems aware of NUMA ([[Non-Uniform Memory Access]]) use this table to allocate local memory to local [[Thread (computer science)|threads]] on NUMA systems, e.g. on multi processor [[AMD Opteron]] systems. For a real [[Non-Uniform Memory Access|NUMA]] system, "Node Interleave" in Opteron BIOSes has to be disabled, accordingly "SRAT" has to be enabled. Furthermore the operating system itself has to support NUMA as well. So far all x64 Windows Systems and Linux systems with a NUMA aware [[Kernel (computer science)|kernel]] are NUMA capable.
;SLIT (System Locality Distance Information Table)
This optional SLIT (System Locality Information Table) describes the distances between all processors, memory controllers, and host bridges. Each module gets associated with specific locality (could tie with the _PXM) which will be equivalent to an [[Symmetric multiprocessing|SMP]] node. The table will give units of distance between nodes. The units of distance will be relative to the SMP or intra-node distance. SMP distances will arbitrarily have a value of 10. There is a field in the table called Localities. Localities is the number of localities in the SLIT. It is an unsigned 64-bit integer. The locality indices for each locality range from 0 to Localities-1. The SLIT can be viewed as a matrix of distances, with row i of the matrix indicating the distance from locality i to every locality (including itself). Each table entry is a 1-byte unsigned integer. To get the distance from locality i to locality j, read the i*(Localities) + j entry in the matrix. Except for the distances from a locality to itself, each distance is stored twice in the matrix.
What this means is that the diagonal elements of the matrix, the distances from a locality to itself, which are the SMP distances, are all given a value of 10. The distances for the non-diagonal elements are scaled to be relative to the SMP distance, so, for example, if the distance from locality i to locality j is 2.4 times the SMP distance, a value of 24 would be stored in table entry i*(localities)+ j and in j*(localities)+ i. If one locality is unreachable from another, a value of 255 (0xFF) will be stored in that table entry. A value of 0 has no meaning, and is reserved. Values 1 through 9 are also reserved. This will enable the operating system to enhance its ability to process the locality information to increase its performance on a NUMA system.
;SLIC (Software Licensing Description Table)
[[Original equipment manufacturer|OEM]] versions of [[Windows Vista]] use this [[as of 2008| newly-released]] table for activation by Royalty OEMs in order for the end-user to not have problems with activating, called SLP 2.0, or System-Locked Preinstallation 2.0. For activation to work, clients obtained through the OEM channels that have an ACPI_SLIC table in the system BIOS are required to have a valid Windows marker in the same ACPI_SLIC table. The appearance of the Windows marker is important for volume license customers who are planning to use Windows Vista volume-licensed media to re-image or upgrade OEM through the re-imaging rights provided in their volume license agreement. Not having the appropriate BIOS marker results in an error or errors on these systems and prevents them from activating.{{cite web |url=http://support.microsoft.com/kb/942962 |title=You receive an error message when you try to activate Windows Vista on a computer that was obtained from an OEM |accessdate=2008-08-04 |publisher=Microsoft |date=2007-11-02 }}
;SSDT (Secondary System Descriptor Table)
== Criticism ==
{{criticism-section}}
* The complex and lengthy ACPI specification (over 600 pages long) contains multiple components, including declarative tables, an imperative [[bytecode]], and specific hardware components. Concerns have been repeatedly raised[http://lwn.net/2001/0704/kernel.php3 LWN - Kernel] that an implementation of ACPI has to run complex, untrusted and potentially buggy bytecode with full privileges, thus potentially making any system that implements ACPI unstable and/or insecure.
* Where hardware does not conform to ACPI, but claims to do so, the software interoperating with that hardware is faced with a dilemma: either it can be written to be ACPI-compliant, thus risking problems with the not-entirely-compliant hardware, or it can deviate from the ACPI standard to accommodate the hardware quirks. That, however, is generally seen as undesirable from a software-engineering point of view, since the software would potentially have to be adapted for and tested with arbitrarily large numbers of hardware devices, which is precisely what standards such as ACPI are intended to avoid. Additionally, availability of compatible software does not provide the hardware manufacturer with an incentive to repair their compliance. This is a constant debate between "standards purists" and advocates of software that "simply works" with as much hardware as possible.
== ACPI Component Architecture (ACPICA) ==
{{Expand-section|date=July 2008}}
The ACPI Component Architecture (ACPICA) is an [[open source]] reference implementation of ACPI.[http://www.acpica.org/ ACPICA]
== See also ==
*[[Green computing]]
*[[Power management keys]]
*[[Wake-on-Ring]]
== References ==
{{reflist}}
== External links ==
* [http://www.acpi.info/ ACPI home page]
* [http://developer.intel.com/technology/iapc/acpi/downloads.htm Intel's ACPI Component Architecture]
* [http://www.lesswatts.org/projects/acpi/ ACPI for Linux]
* [http://www.freebsd.org/cgi/man.cgi?query=acpi&format=html ACPI for FreeBSD]
* [http://www.advogato.org/article/913.html How Linux Suspend and Resume works in the ACPI age]
* [http://www.hardwaresecrets.com/article/611 Everything You Need to Know About the CPU C-States Power Saving Modes]
{{FOLDOC}}
[[Category:BIOS]]
[[Category:Application programming interfaces]]
[[Category:Open standards]]
[[de:Advanced Configuration and Power Interface]]
[[es:Advanced Configuration and Power Interface]]
[[fa:رابط قدرت و تنظیمات پیشرفته]]
[[fr:Advanced Configuration and Power Interface]]
[[ko:ACPI]]
[[id:ACPI]]
[[it:Advanced Configuration and Power Interface]]
[[ja:Advanced Configuration and Power Interface]]
[[no:Advanced Configuration and Power Interface]]
[[pl:ACPI]]
[[pt:ACPI]]
[[ru:ACPI]]
[[sk:Advanced Configuration and Power Interface]]
[[fi:ACPI]]
[[sv:Advanced Configuration and Power Interface]]
[[uk:ACPI]]
[[zh:高级配置与电源接口]]
没有评论:
发表评论