Lines Matching full:frequency
19 different clock frequency and voltage configurations, often referred to as
21 the higher the clock frequency and the higher the voltage, the more instructions
23 frequency and the higher the voltage, the more energy is consumed over a unit of
30 highest one (i.e. the highest-performance frequency/voltage configuration
37 different frequency/voltage configurations or (in the ACPI terminology) to be
44 to as CPU performance scaling or CPU frequency scaling (because it involves
45 adjusting the CPU clock frequency).
52 (CPU Frequency scaling) subsystem that consists of three layers of code: the
244 Current frequency of the CPUs belonging to this policy as obtained from
247 This is expected to be the frequency the hardware actually runs at.
248 If that frequency cannot be determined, this attribute should not
252 Maximum possible operating frequency the CPUs belonging to this policy
256 Minimum possible operating frequency the CPUs belonging to this policy
285 Current frequency of all of the CPUs belonging to this policy (in kHz).
287 In the majority of cases, this is the frequency of the last P-state
289 interface provided by it, which may or may not reflect the frequency
294 more precisely reflecting the current CPU frequency through this
295 attribute, but that still may not be the exact current CPU frequency as
314 Maximum frequency the CPUs belonging to this policy are allowed to be
322 Minimum frequency the CPUs belonging to this policy are allowed to be
333 It returns the last frequency requested by the governor (in kHz) or can
334 be written to in order to set a new frequency for the policy.
364 When attached to a policy object, this governor causes the highest frequency,
374 When attached to a policy object, this governor causes the lowest frequency,
385 to set the CPU frequency for the policy it is attached to by writing to the
396 invoke the scaling driver asynchronously when it decides that the CPU frequency
398 is capable of changing the CPU frequency from scheduler context).
402 RT or deadline scheduling classes, the governor will increase the frequency to
408 CPU frequency to apply is computed in accordance with the formula
413 ``util``, and ``f_0`` is either the maximum possible CPU frequency for the given
414 policy (if the PELT number is frequency-invariant), or the current CPU frequency
418 CPU frequency for tasks that have been waiting on I/O most recently, called
420 is passed by the scheduler to the governor callback which causes the frequency
444 This governor uses CPU load as a CPU frequency selection metric.
468 speedup threshold, in which case it will go straight for the highest frequency
491 will set the frequency to the maximum value allowed for the policy.
492 Otherwise, the selected frequency will be proportional to the estimated
501 taken into account when deciding what frequency to run the CPUs at.
510 setting the frequency to the allowed maximum) to be delayed, so the
511 frequency stays at the maximum level for a longer time.
513 Frequency fluctuations in some bursty workloads may be avoided this way
518 Reduction factor to apply to the original frequency target of the
521 for the AMD frequency sensitivity powersave bias driver
525 If the AMD frequency sensitivity powersave bias driver is not loaded,
526 the effective frequency to apply is given by
530 where f is the governor's original frequency target. The default value
533 If the AMD frequency sensitivity powersave bias driver is loaded, the
540 workload running on a CPU will change in response to frequency changes.
544 the CPU frequency, whereas workloads with the sensitivity of 100%
545 (CPU-bound) are expected to perform much better if the CPU frequency is
550 will cause the governor to select a frequency lower than its original
557 This governor uses CPU load as a CPU frequency selection metric.
560 above, but the CPU frequency selection algorithm implemented by it is different.
562 Namely, it avoids changing the frequency significantly over short time intervals
564 battery-powered). To achieve that, it changes the frequency in relatively
571 Frequency step in percent of the maximum frequency the governor is
575 This is how much the frequency is allowed to change in one go. Setting
576 it to 0 will cause the default frequency step (5 percent) to be used
578 switch the frequency between the ``scaling_min_freq`` and
583 frequency change direction.
585 If the estimated CPU load is greater than this value, the frequency will
587 ``sampling_down_factor`` mechanism is not in effect), the frequency will
588 go down. Otherwise, the frequency will not be changed.
591 Frequency decrease deferral factor, between 1 (default) and 10
594 It effectively causes the frequency to go down ``sampling_down_factor``
598 Frequency Boost Support
604 Some processors support a mechanism to raise the operating frequency of some
605 cores in a multicore package temporarily (and above the sustainable frequency
613 term "frequency boost" is used here for brevity to refer to all of those
616 The frequency boost mechanism may be either hardware-based or software-based.
619 into a special state in which it can control the CPU frequency within certain
628 scaling driver does not support the frequency boost mechanism (or supports it,
632 If the value in this file is 1, the frequency boost mechanism is enabled. This
637 permission to use the frequency boost mechanism (which still may never be used
640 If the value in this file is 0, the frequency boost mechanism is disabled and
648 The frequency boost mechanism is generally intended to help to achieve optimum
653 For this reason, many systems make it possible to disable the frequency boost
660 as a result of increasing its frequency and voltage, even temporarily.
670 3. To examine the impact of the frequency boost mechanism itself, it is useful
678 frequency boost mechanism before running benchmarks sensitive to that