27.10.2015 Views

Advanced Configuration and Power Interface Specification

ACPI_6.0

ACPI_6.0

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Device <strong>Configuration</strong><br />

This optional object is used to describe proximity domains within a machine. _PXM evaluates to an<br />

integer that identifies the device as belonging to a specific proximity domain. OSPM assumes that<br />

two devices in the same proximity domain are tightly coupled. OSPM could choose to optimize its<br />

behavior based on this. For example, in a system with four processors <strong>and</strong> six memory devices, there<br />

might be two separate proximity domains (0 <strong>and</strong> 1), each with two processors <strong>and</strong> three memory<br />

devices. In this case, the OS may decide to run some software threads on the processors in proximity<br />

domain 0 <strong>and</strong> others on the processors in proximity domain 1. Furthermore, for performance<br />

reasons, it could choose to allocate memory for those threads from the memory devices inside the<br />

proximity domain common to the processor <strong>and</strong> the memory device rather than from a memory<br />

device outside of the processor’s proximity domain. _PXM can be used to identify any device<br />

belonging to a proximity domain. Children of a device belong to the same proximity domain as their<br />

parent unless they contain an overriding _PXM. Proximity domains do not imply any ejection<br />

relationships.<br />

An OS makes no assumptions about the proximity or nearness of different proximity domains. The<br />

difference between two integers representing separate proximity domains does not imply distance<br />

between the proximity domains (in other words, proximity domain 1 is not assumed to be closer to<br />

proximity domain 0 than proximity domain 6).<br />

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

dynamically added processor is not present in the System Resource Affinity Table (SRAT), a _PXM<br />

object must exist for the processor’s device or one of its ancestors in the ACPI Namespace.<br />

Arguments:<br />

None<br />

Return Value:<br />

An Integer (DWORD) containing a proximity domain identifier.<br />

6.2.15 _SLI (System Locality Information)<br />

The System Locality Information Table (SLIT) table defined in Section 5.2.17, “System Locality<br />

Distance Information Table (SLIT)” provides relative distance information between all System<br />

Localities for use during OS initialization.<br />

The value of each Entry[i,j] in the SLIT table, where i represents a row of a matrix <strong>and</strong> j represents a<br />

column of a matrix, indicates the relative distances from System Locality / Proximity Domain i to<br />

every other System Locality j in the system (including itself).<br />

The i,j row <strong>and</strong> column values correlate to the value returned by the _PXM object in the ACPI<br />

namespace. See Section 6.2.14, “_PXM (Proximity)” for more information.<br />

Dynamic runtime reconfiguration of the system may cause the distance between System Localities<br />

to change.<br />

_SLI is an optional object that enables the platform to provide the OS with updated relative System<br />

Locality distance information at runtime. _SLI provide OSPM with an update of the relative distance<br />

from System Locality i to all other System Localities in the system.<br />

Arguments:<br />

None<br />

Version 6.0 325

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

Saved successfully!

Ooh no, something went wrong!