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 />

Device(EC0) {<br />

Name(REGC,Ones)<br />

Method(_REG,2) {<br />

If(Lequal(Arg0, 3)) {<br />

Store(Arg1, REGC)<br />

}<br />

}<br />

}<br />

Method(ECAV,0) {<br />

If(Lequal(REGC,Ones)) {<br />

If(LgreaterEqual(_REV,2)) {<br />

Return(One)<br />

}<br />

Else {<br />

Return(Zero)<br />

}<br />

}<br />

Else {<br />

Return(REGC)<br />

}<br />

}<br />

To detect the availability of the region, call the ECAV method. For example:<br />

If (\_SB.PCI0.EC0.ECAV()) {<br />

...regions are available...<br />

}<br />

else {<br />

...regions are not available...<br />

}<br />

5.2.16 System Resource Affinity Table (SRAT)<br />

This optional table provides information that allows OSPM to associate processors <strong>and</strong> memory<br />

ranges, including ranges of memory provided by hot-added memory devices, with system localities /<br />

proximity domains <strong>and</strong> clock domains. On NUMA platforms, SRAT information enables OSPM to<br />

optimally configure the operating system during a point in OS initialization when evaluation of<br />

objects in the ACPI Namespace is not yet possible. OSPM evaluates the SRAT only during OS<br />

initialization. The Local APIC ID / Local SAPIC ID / Local x2APIC ID or the GICC ACPI<br />

Processor UID of all processors started at boot time must be present in the SRAT. If the Local APIC<br />

ID / Local SAPIC ID / Local x2APIC ID or the GICC ACPI Processor UID of a dynamically added<br />

processor is not present in the SRAT, a _PXM object must exist for the processor’s device or one of<br />

its ancestors in the ACPI Namespace.<br />

Table 5-70 Static Resource Affinity Table Format<br />

Field<br />

Byte<br />

Length<br />

Byte<br />

Offset<br />

Description<br />

Header<br />

Signature 4 0 ‘SRAT’. Signature for the System Resource Affinity Table.<br />

Length 4 4 Length, in bytes, of the entire SRAT. The length implies the<br />

number of Entry fields at the end of the table<br />

Revision 1 8 3<br />

Checksum 1 9 Entire table must sum to zero.<br />

158 April, 2015 Version 6.0

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

Saved successfully!

Ooh no, something went wrong!