18.12.2012 Views

Advanced Configuration and Power Interface Specification

Advanced Configuration and Power Interface Specification

Advanced Configuration and Power Interface Specification

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.

ACPI-Defined Devices <strong>and</strong> Device-Specific Objects<br />

when the platform supports memory b<strong>and</strong>width monitoring <strong>and</strong> reporting (see Section 9.12.2,<br />

“Memory B<strong>and</strong>width Monitoring <strong>and</strong> Reporting). Memory devices may describe exactly the same<br />

physical memory that the System Address Map interfaces describe (see section 14, “System Address<br />

Map <strong>Interface</strong>s”). They do not describe how that memory is, or has been, used. If a region of<br />

physical memory is marked in the System Address Map interface as AddressRangeReserved or<br />

AddressRangeNVS <strong>and</strong> it is also described in a memory device, then it is the responsibility of the<br />

OS to guarantee that the memory device is never disabled.<br />

It is not necessary to describe all memory in the system with memory devices if there is some<br />

memory in the system that is static in nature. If, for instance, the memory that is used for the first 16<br />

MB of system RAM cannot be ejected, inserted, or disabled, that memory may only be represented<br />

by the System Address Map interfaces. But if memory can be ejected, inserted, or disabled, or if the<br />

platform supports memory b<strong>and</strong>width monitoring <strong>and</strong> reporting, the memory must be represented by<br />

a memory device.<br />

9.12.1 Address Decoding<br />

Memory devices must provide a _CRS object that describes the physical address space that the<br />

memory decodes. If the memory can decode alternative ranges in physical address space, the devices<br />

may also provide _PRS, _SRS <strong>and</strong> _DIS objects. Other device objects may also apply if the device<br />

can be ejected.<br />

9.12.2 Memory B<strong>and</strong>width Monitoring <strong>and</strong> Reporting<br />

During platform operation, an adverse condition external to the platform may arise whose remedy<br />

requires a reduction in the platform’s available memory b<strong>and</strong>width. For example, a server<br />

management controller’s detection of an adverse thermal condition or the need to reduce the total<br />

power consumption of platforms in the data center to stay within acceptable limits. Providing OSPM<br />

with knowledge of a platform induced reduction of memory b<strong>and</strong>width enables OSPM to provide<br />

more robust h<strong>and</strong>ling of the condition. The following sections describe objects OSPM uses to<br />

configure platform-based memory b<strong>and</strong>width monitoring <strong>and</strong> to ascertain available memory<br />

b<strong>and</strong>width when the platform performs memory b<strong>and</strong>width throttling.<br />

9.12.2.1 _MBM (Memory B<strong>and</strong>width Monitoring Data)<br />

The optional _MBM object provides memory b<strong>and</strong>width monitoring information for the memory<br />

device.<br />

Arguments:<br />

None<br />

Return Value:<br />

A Package containing memory device status information as described in Table 9-224 below<br />

Return Value Information:<br />

_MBM evaluation returns a package of the following format:<br />

458 Hewlett-Packard/Intel/Microsoft/Phoenix/Toshiba

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

Saved successfully!

Ooh no, something went wrong!