27.10.2015 Views

Advanced Configuration and Power Interface Specification

ACPI_6.0

ACPI_6.0

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Advanced</strong> <strong>Configuration</strong> <strong>and</strong> <strong>Power</strong> <strong>Interface</strong> <strong>Specification</strong><br />

hierarchy is herein referred to as a node. The processor container device is declared using the<br />

hardware identifier (_HID) ACPI0010.<br />

To aid support of operating systems which do not parse processor containers, a container can carry a<br />

Compatible ID (_CID) of PNP0A05, which represents a generic container device (see Section 5.6.7)<br />

A processor container declaration must supply a _UID method returning an ID that is unique in the<br />

processor container hierarchy. A processor container must contain either other processor containers<br />

or other processor devices declared within its scope. In addition, a processor container may also<br />

contain the following methods in its scope:<br />

Table 8-238 Processor Container Device Objects<br />

Object Description<br />

_LPI Declares local power states for the hierarchy node represented by the processor container<br />

_RDI Declares power resource dependencies that affect system level power states<br />

_STA Determines the status of a processor container. See Section 5.6.7,<br />

_LPI may be present under a processor device, <strong>and</strong> is described in Section 8.4.4.3 _RDI can only be<br />

present under a singular top level processor container object, <strong>and</strong> is described below.<br />

ACPI allows the definition of more than one root level processor container. In other words, it is<br />

possible to define multiple top level containers. For example, in a NUMA system if there are no idle<br />

states or other objects that need to be encapsulated at the system level, multiple NUMA-node level<br />

processor containers may be defined at the top level of the hierarchy.<br />

Processor Container Device objects are only valid for implementations conforming to ACPI 6.0 or<br />

higher. A platform can ascertain whether an operating system supports parsing of processor<br />

container objects via the _OSC method (see Section 6.2.11.2).<br />

8.4.4 Lower <strong>Power</strong> Idle States<br />

ACPI 6.0 introduces Lower <strong>Power</strong> Idle states (LPI). This extends the specification to allow<br />

expression of idle states that, like C-states, are selected by the OSPM when a processor goes idle, but<br />

which may affect more than one processor, <strong>and</strong> may affect other system components. LPI extensions<br />

in the specification leverage the processor container device, <strong>and</strong> in this way can express which parts<br />

of the system are affected by a given LPI state.<br />

LPI states are defined via the following objects:<br />

• _LPI objects define the states themselves, <strong>and</strong> may be declared inside a processor or a processor<br />

container device<br />

• _RDI allows expressing constraints on LPI usage borne out of device usage<br />

8.4.4.1 Hierarchical Idle States<br />

Processor containers (Section 8.4.3.1) can be used in conjunction with _LPI (Section 8.4.4.3) to<br />

describe idle states in a hierarchical manner. Within the processor hierarchy, each node has low<br />

power states that are specific to that node. ACPI refers to states that are specific to a node in the<br />

hierarchy as Local <strong>Power</strong> States. For example in the system depicted in Figure 8-46, the local power<br />

states of CPU0 are clock gate, retention <strong>and</strong> power down.<br />

436 April, 2015 Version 6.0

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!