Lines Matching full:states
27 information about that). For this reason, the representation of P-states used
32 ``intel_pstate`` maps its internal representation of P-states to frequencies too
69 hardware-managed P-states (HWP) support. If it works in this mode, the
89 depends on whether or not the hardware-managed P-states (HWP) feature has been
106 select P-states by itself, but still it can give hints to the processor's
130 Also, in this configuration the range of P-states available to the processor's
182 registers of the CPU. It generally selects P-states proportional to the
199 hardware-managed P-states (HWP) support. It is always used if the
223 the entire range of available P-states is exposed by ``intel_pstate`` to the
232 Turbo P-states Support
235 In the majority of cases, the entire range of P-states available to
240 The P-states above the turbo threshold are referred to as "turbo P-states" and
241 the whole sub-range of P-states they belong to is referred to as the "turbo
249 performance scaling control for that core and put it into turbo P-states of its
252 processors will never use any P-states above the last one set by software for
254 processor generations will take it as a license to use any P-states from the
257 to put the given core into all turbo P-states up to and including the maximum
260 One important property of turbo P-states is that they are not sustainable. More
262 those states indefinitely, because the power distribution within the processor
266 In turn, the P-states below the turbo threshold generally are sustainable. In
272 Some processors allow multiple cores to be in turbo P-states at the same time,
289 the entire range of available P-states, including the whole turbo range, to the
291 generally causes turbo P-states to be set more often when ``intel_pstate`` is
298 work as expected in all cases (that is, if set to disable turbo P-states, it
312 * Whether or not turbo P-states are supported at all.
314 * The maximum supported `one-core turbo P-state <turbo_>`_ (if turbo P-states
318 of P-states into frequencies and the other way around.
364 Number of P-states supported by the processor (between 0 and 255
365 inclusive) including both turbo and non-turbo P-states (see
366 `Turbo P-states Support`_).
378 range of supported P-states, in percent.
388 If set (equal to 1), the driver is not allowed to set any turbo P-states
389 (see `Turbo P-states Support`_). If unset (equal to 0, which is the
390 default), turbo P-states can be set by the driver.
466 not allowed to use turbo P-states, so the maximum value of ``scaling_max_freq``
525 P-states, hyper-threading is enabled and on current performance requests
526 from other CPUs. When platform doesn't support per core P-states, the
529 core P-states support, when hyper-threading is enabled, if the sibling CPU
538 set P-states within these limits. Otherwise, the limits are taken into account
550 If the hardware-managed P-states (HWP) is enabled in the processor, additional
599 interface, but the set of P-states it can use is limited by the ``_PSS``
602 On those systems each ``_PSS`` object returns a list of P-states supported by
603 the corresponding CPU which basically is a subset of the P-states range that can
612 The list of P-states returned by ``_PSS`` is reflected by the table of
624 (possibly multiplied by a constant), then it will tend to choose P-states below
629 benefit from running at turbo frequencies will be given non-turbo P-states
634 turbo threshold. Namely, if that is not coordinated with the lists of P-states
638 P-states overall, ``acpi-cpufreq`` simply avoids using the topmost state listed
639 by ``_PSS``, but that is not sufficient when there are other turbo P-states in
643 `passive mode <Passive Mode_>`_, except that the number of P-states it can set
671 power capping) that rely on the availability of ACPI P-states
680 Do not enable the hardware-managed P-states (HWP) feature even if it is
685 hardware-managed P-states (HWP) feature is supported by the processor.