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.

Processor <strong>Configuration</strong> <strong>and</strong> Control<br />

need to stay in the idle state to overcome the energy cost of transitioning in/out, <strong>and</strong> make choosing<br />

that state a net win relative to shallower alternatives? Note that this also includes comparing against<br />

not entering an idle state <strong>and</strong> keeping the node running. This is illustrated in Figure 8-48 which<br />

shows the energy associated with three different state choices as a function of the sleep duration.<br />

Note that State A’s MR relative to keeping the node running is not pictured.<br />

Generally minimum residency <strong>and</strong> worst case wakeup latency will be larger for deeper states,<br />

however this may not always be the case. Taking a different example to the above, consider two<br />

system level states, StateY <strong>and</strong> StateZ, with similar entry overhead but where StateZ saves more<br />

power than StateY. An abstract state list might look like:<br />

StateX: MR = 100 us<br />

StateY: MR = 1000 us<br />

StateZ: MR = 800 us, power resource A must be OFF<br />

From an energy perspective, StateZ is always preferred, but in this example, StateZ is only available<br />

when certain device dependencies are met. This makes StateY attractive when the dependencies<br />

cannot be met. Despite being the deeper (lower power) state, StateZ has a lower MR than StateY<br />

since the entry overheads are similar <strong>and</strong> StateZ’s lower power more quickly amortizes the transition<br />

cost. Although the crossover, which sets MR, should generally be versus the next shallowest state,<br />

MR is defined relative to any shallower (higher power) state to deal with cases like this. In this case,<br />

StateZ’s MR is set by the crossover with StateX since StateZ (if allowed based on device<br />

dependencies) is always preferred to StateY. To achieve the lowest energy, OSPM must select the<br />

deepest (lowest power) state for which all entry constraints are satisfied <strong>and</strong> should not assume that<br />

deeper states are not viable just because a shallower state’s WCWL/MR threshold was not met.<br />

Since WCWL may be used by OSPM to restrict idle state selection <strong>and</strong> guarantee response times to<br />

critical interrupts, it should be set conservatively (erring on the high side) so that OSPM is not<br />

surprised with worse than specified interrupt response time. On the other h<strong>and</strong>, MR helps OSPM<br />

make efficient decisions. If MR is inaccurate in a certain scenario <strong>and</strong> OSPM chooses a state which<br />

is deeper or shallower than optimal for a particular idle period, there may be some wasted energy but<br />

the system will not be functionally broken. This is not to say that MR doesn’t matter –energy<br />

efficiency is important – just that the platform may choose to optimize MR based on the typical case<br />

rather than the worst case.<br />

8.4.4.3.3.1 Minimum Residency <strong>and</strong> Worst Case Wakeup Latency Combination Across Hierarchy<br />

Levels<br />

The WCWL in _LPI is for a particular local state. When evaluating composite state choices versus<br />

system latency tolerance as part of idle state selection, OSPM will add wakeup latencies across<br />

hierarchy levels. For example, if a system has core powerdown with WCWL = 50 us <strong>and</strong> cluster<br />

powerdown with WCWL = 20 us then the core powerdown + cluster powerdown composite state<br />

latency is calculated as 70 us.<br />

MRs defined in _LPI apply to a particular hierarchy node. The implicit assumption is that each<br />

hierarchy node represents an independent power manageable domain <strong>and</strong> can be considered<br />

separately. For example, assume that a cluster retention state is legal if the underlying cores are in<br />

core powerdown or core retention. The MR for cluster retention is based on the energy cost of taking<br />

shared logic outside of the cores in <strong>and</strong> out of retention versus the steady state power savings<br />

achieved in that shared logic while in that state. The key is that the specific state chosen at the core<br />

level does not fundamentally affect the cluster level decision since it is tied to properties of shared<br />

Version 6.0 449

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

Saved successfully!

Ooh no, something went wrong!