Lines Matching full:governor
60 As a rule, each governor implements one, possibly parametrized, scaling
81 to bypass the governor layer and implement their own performance scaling
148 scaling governor to it (to begin with, that is the default scaling governor
151 the governor's ``->init()`` callback which is expected to initialize all of the
153 a governor ``sysfs`` interface to it. Next, the governor is started by
166 on the configuration and capabilities of the scaling driver and the governor.
171 to use the scaling governor previously used with the policy that became
172 "inactive" (and is re-initialized now) instead of the default governor.
177 necessary to restart the scaling governor so that it can take the new online CPU
178 into account. That is achieved by invoking the governor's ``->stop`` and
182 governor layer of ``CPUFreq`` and provides its own P-state selection algorithms.
216 and what scaling governor is attached to the given policy. Some scaling drivers
264 work with the `ondemand`_ governor, -1 (:c:macro:`CPUFREQ_ETERNAL`)
281 kernel module for the governor held by it to become available and be
302 The scaling governor currently attached to this policy or (if the
307 governor to be attached to this policy or a new scaling algorithm
330 This attribute is functional only if the `userspace`_ scaling governor
333 It returns the last frequency requested by the governor (in kHz) or can
348 The scaling governor for a given policy object can be changed at any time with
352 algorithms implemented by them. Those attributes, referred to as governor
354 scaling driver in use. If the driver requires governor tunables to be
358 subdirectory containing the governor tunables is the name of the governor
364 When attached to a policy object, this governor causes the highest frequency,
367 The request is made once at that time the governor for the policy is set to
374 When attached to a policy object, this governor causes the lowest frequency,
377 The request is made once at that time the governor for the policy is set to
384 This governor does not do anything by itself. Instead, it allows user space
391 This governor uses CPU utilization data available from the CPU scheduler. It
400 The actions of this governor for a particular CPU depend on the scheduling class
402 RT or deadline scheduling classes, the governor will increase the frequency to
404 if it is invoked by the CFS scheduling class, the governor will use the
417 This governor also employs a mechanism allowing it to temporarily bump up the
420 is passed by the scheduler to the governor callback which causes the frequency
424 This governor exposes only one tunable:
428 runs of governor computations (default: 1.5 times the scaling driver's
432 of the governor which might be excessive without it.
434 This governor generally is regarded as a replacement for the older `ondemand`_
444 This governor uses CPU load as a CPU frequency selection metric.
451 If this governor is attached to a policy shared by multiple CPUs, the load is
455 The worker routine of this governor has to run in process context, so it is
458 governor is minimum, but it causes additional CPU context switches to happen
471 This governor exposes the following tunables:
474 This is how often the governor's worker routine should run, in
479 to ``cpuinfo_transition_latency`` on each policy this governor is
490 If the estimated CPU load is above this value (in percent), the governor
509 This causes the next execution of the governor's worker routine (after
519 governor (including the maximum value used when the ``up_threshold``
530 where f is the governor's original frequency target. The default value
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.
559 It estimates the CPU load in the same way as the `ondemand`_ governor described
568 This governor exposes the following tunables:
571 Frequency step in percent of the maximum frequency the governor is
577 and setting it to 100 effectively causes the governor to periodically