Lines Matching refs:scaling

17 :doc:`CPU performance scaling subsystem <cpufreq>` in the Linux kernel
18 (``CPUFreq``).  It is a scaling driver for the Sandy Bridge and later
50 ``sysfs`` which allows another ``CPUFreq`` scaling driver to be loaded and
69 In this mode the driver bypasses the scaling governors layer of ``CPUFreq`` and
70 provides its own scaling algorithms for P-state selection.  Those algorithms
71 can be applied to ``CPUFreq`` policies in the same way as generic scaling
76 They are not generic scaling governors, but their names are the same as the
173 implemented by the generic ``schedutil`` scaling governor except that the
198 Then, the driver behaves like a regular ``CPUFreq`` scaling driver.  That is,
199 it is invoked by generic scaling governors when necessary to talk to the
204 scaling governors listed by the ``scaling_available_governors`` policy attribute
207 corresponding to CPUs and provides the ``CPUFreq`` core (and the scaling
215 by the current scaling governor for the given policy).
237 performance scaling control for that core and put it into turbo P-states of its
278 ``CPUFreq`` core and (in the passive mode) to generic scaling governors.  This
280 used relative to ACPI-based CPU performance scaling (see `below <acpi-cpufreq_>`_
305  * The scaling formula to translate the driver's internal representation
375 	attribute (supported by some other scaling drivers) which is replaced
408 		The driver is not functional (it is not registered as a scaling
432 :doc:`cpufreq` is special with ``intel_pstate`` as the current scaling driver
478 same as for other scaling drivers.
516 scaling governors (in the `passive mode <Passive Mode_>`_) and by the driver
566 that can be used for CPU performance scaling (refer to the ACPI specification
571 ``acpi-cpufreq`` scaling driver.  On systems supported by ``intel_pstate``
572 the ``acpi-cpufreq`` driver uses the same hardware CPU performance scaling
588 scaling governors and the minimum and maximum supported frequencies reported by
593 affects decisions made by the scaling governors, except for ``powersave`` and
599 the turbo threshold if ``acpi-cpufreq`` is used as the scaling driver, because
629 	Do not register ``intel_pstate`` as the scaling driver even if the
639 	Register ``intel_pstate`` as the scaling driver instead of
648 	``intel_pstate`` and on platforms where the ``pcc-cpufreq`` scaling
656 	Register ``intel_pstate`` as the scaling driver only if the
697 scaling governor (for the policies it is attached to), or by the ``CPUFreq``
698 core (for the policies with other scaling governors).