Lines Matching full:frequency
16 different clock frequency and voltage configurations, often referred to as
18 the higher the clock frequency and the higher the voltage, the more instructions
20 frequency and the higher the voltage, the more energy is consumed over a unit of
27 highest one (i.e. the highest-performance frequency/voltage configuration
34 different frequency/voltage configurations or (in the ACPI terminology) to be
41 to as CPU performance scaling or CPU frequency scaling (because it involves
42 adjusting the CPU clock frequency).
49 (CPU Frequency scaling) subsystem that consists of three layers of code: the
241 Current frequency of the CPUs belonging to this policy as obtained from
244 This is expected to be the frequency the hardware actually runs at.
245 If that frequency cannot be determined, this attribute should not
249 Maximum possible operating frequency the CPUs belonging to this policy
253 Minimum possible operating frequency the CPUs belonging to this policy
278 Current frequency of all of the CPUs belonging to this policy (in kHz).
280 In the majority of cases, this is the frequency of the last P-state
282 interface provided by it, which may or may not reflect the frequency
287 more precisely reflecting the current CPU frequency through this
288 attribute, but that still may not be the exact current CPU frequency as
307 Maximum frequency the CPUs belonging to this policy are allowed to be
315 Minimum frequency the CPUs belonging to this policy are allowed to be
326 It returns the last frequency requested by the governor (in kHz) or can
327 be written to in order to set a new frequency for the policy.
357 When attached to a policy object, this governor causes the highest frequency,
367 When attached to a policy object, this governor causes the lowest frequency,
378 to set the CPU frequency for the policy it is attached to by writing to the
389 invoke the scaling driver asynchronously when it decides that the CPU frequency
391 is capable of changing the CPU frequency from scheduler context).
395 RT or deadline scheduling classes, the governor will increase the frequency to
401 CPU frequency to apply is computed in accordance with the formula
406 ``util``, and ``f_0`` is either the maximum possible CPU frequency for the given
407 policy (if the PELT number is frequency-invariant), or the current CPU frequency
411 CPU frequency for tasks that have been waiting on I/O most recently, called
413 is passed by the scheduler to the governor callback which causes the frequency
437 This governor uses CPU load as a CPU frequency selection metric.
461 speedup threshold, in which case it will go straight for the highest frequency
484 will set the frequency to the maximum value allowed for the policy.
485 Otherwise, the selected frequency will be proportional to the estimated
494 taken into account when deciding what frequency to run the CPUs at.
503 setting the frequency to the allowed maximum) to be delayed, so the
504 frequency stays at the maximum level for a longer time.
506 Frequency fluctuations in some bursty workloads may be avoided this way
511 Reduction factor to apply to the original frequency target of the
514 for the AMD frequency sensitivity powersave bias driver
518 If the AMD frequency sensitivity powersave bias driver is not loaded,
519 the effective frequency to apply is given by
523 where f is the governor's original frequency target. The default value
526 If the AMD frequency sensitivity powersave bias driver is loaded, the
533 workload running on a CPU will change in response to frequency changes.
537 the CPU frequency, whereas workloads with the sensitivity of 100%
538 (CPU-bound) are expected to perform much better if the CPU frequency is
543 will cause the governor to select a frequency lower than its original
550 This governor uses CPU load as a CPU frequency selection metric.
553 above, but the CPU frequency selection algorithm implemented by it is different.
555 Namely, it avoids changing the frequency significantly over short time intervals
557 battery-powered). To achieve that, it changes the frequency in relatively
564 Frequency step in percent of the maximum frequency the governor is
568 This is how much the frequency is allowed to change in one go. Setting
569 it to 0 will cause the default frequency step (5 percent) to be used
571 switch the frequency between the ``scaling_min_freq`` and
576 frequency change direction.
578 If the estimated CPU load is greater than this value, the frequency will
580 ``sampling_down_factor`` mechanism is not in effect), the frequency will
581 go down. Otherwise, the frequency will not be changed.
584 Frequency decrease deferral factor, between 1 (default) and 10
587 It effectively causes the frequency to go down ``sampling_down_factor``
591 Frequency Boost Support
597 Some processors support a mechanism to raise the operating frequency of some
598 cores in a multicore package temporarily (and above the sustainable frequency
606 term "frequency boost" is used here for brevity to refer to all of those
609 The frequency boost mechanism may be either hardware-based or software-based.
612 into a special state in which it can control the CPU frequency within certain
621 scaling driver does not support the frequency boost mechanism (or supports it,
625 If the value in this file is 1, the frequency boost mechanism is enabled. This
630 permission to use the frequency boost mechanism (which still may never be used
633 If the value in this file is 0, the frequency boost mechanism is disabled and
641 The frequency boost mechanism is generally intended to help to achieve optimum
646 For this reason, many systems make it possible to disable the frequency boost
653 as a result of increasing its frequency and voltage, even temporarily.
663 3. To examine the impact of the frequency boost mechanism itself, it is useful
671 frequency boost mechanism before running benchmarks sensitive to that