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.

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

Note: [Hypervisor Vendor Identity ] A firmware implementer would place zero bytes into this field,<br />

denoting that no hypervisor is present in the actual firmware.<br />

Note: [Hypervisor Vendor Identity ] A hypervisor vendor that presents ACPI tables of its own construction<br />

to a guest (for 'virtual' firmware or its 'virtual' platform), would provide its identity in this field.<br />

Note: [Hypervisor Vendor Identity ] If a guest operating system is aware of this field it can consult it <strong>and</strong><br />

act on the result, based on whether it recognized the vendor <strong>and</strong> knows how to use the API that is<br />

defined by the vendor.<br />

Table 5-35 Fixed ACPI Description Table Fixed Feature Flags<br />

FACP - Flag<br />

Bit<br />

Length<br />

Bit<br />

Offset<br />

Description<br />

WBINVD 1 0 Processor properly implements a functional equivalent to the<br />

WBINVD IA-32 instruction.<br />

If set, signifies that the WBINVD instruction correctly flushes<br />

the processor caches, maintains memory coherency, <strong>and</strong><br />

upon completion of the instruction, all caches for the current<br />

processor contain no cached data other than what OSPM<br />

references <strong>and</strong> allows to be cached. If this flag is not set, the<br />

ACPI OS is responsible for disabling all ACPI features that<br />

need this function. This field is maintained for ACPI 1.0<br />

processor compatibility on existing systems. Processors in<br />

new ACPI-compatible systems are required to support this<br />

function <strong>and</strong> indicate this to OSPM by setting this field.<br />

WBINVD_FLUSH 1 1 If set, indicates that the hardware flushes all caches on the<br />

WBINVD instruction <strong>and</strong> maintains memory coherency, but<br />

does not guarantee the caches are invalidated. This provides<br />

the complete semantics of the WBINVD instruction, <strong>and</strong><br />

provides enough to support the system sleeping states. If<br />

neither of the WBINVD flags is set, the system will require<br />

FLUSH_SIZE <strong>and</strong> FLUSH_STRIDE to support sleeping<br />

states. If the FLUSH parameters are also not supported, the<br />

machine cannot support sleeping states S1, S2, or S3.<br />

PROC_C1 1 2 A one indicates that the C1 power state is supported on all<br />

processors.<br />

P_LVL2_UP 1 3 A zero indicates that the C2 power state is configured to only<br />

work on a uniprocessor (UP) system. A one indicates that the<br />

C2 power state is configured to work on a UP or<br />

multiprocessor (MP) system.<br />

PWR_BUTTON 1 4 A zero indicates the power button is h<strong>and</strong>led as a fixed<br />

feature programming model; a one indicates the power button<br />

is h<strong>and</strong>led as a control method device. If the system does not<br />

have a power button, this value would be “1” <strong>and</strong> no sleep<br />

button device would be present.<br />

Independent of the value of this field, the presence of a power<br />

button device in the namespace indicates to OSPM that the<br />

power button is h<strong>and</strong>led as a control method device.<br />

124 April, 2015 Version 6.0

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

Saved successfully!

Ooh no, something went wrong!