Lines Matching full:turbo
222 the so-called "turbo" frequency ranges). In other words, in the passive mode
232 Turbo P-states Support
238 will be referred to as the "turbo threshold" in what follows.
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
242 range". These names are related to the Turbo Boost technology allowing a
247 Specifically, if software sets the P-state of a CPU core within the turbo range
248 (that is, above the turbo threshold), the processor is permitted to take over
249 performance scaling control for that core and put it into turbo P-states of its
253 the given core, even if it is within the turbo range, whereas all of the later
255 turbo range, even above the one set by software. In other words, on those
256 processors setting any P-state from the turbo range will enable the processor
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
264 be exceeded if a turbo P-state was used for too long.
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,
274 of cores running concurrently. The maximum turbo P-state that can be set for 3
276 2 cores, which in turn usually is lower than the maximum turbo P-state that can
277 be set for 1 core. The one-core maximum turbo P-state is thus the maximum
280 The maximum supported turbo P-state, the turbo threshold (the maximum supported
281 non-turbo P-state) and the minimum supported P-state are specific to the
284 (Thermal Design Power) feature and, when that feature is enabled, the turbo
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
295 Moreover, since ``intel_pstate`` always knows what the real turbo threshold is
298 work as expected in all cases (that is, if set to disable turbo P-states, it
310 * The maximum supported `non-turbo P-state <turbo_>`_.
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
336 cores differing by the maximum turbo P-state, performance vs power characteristics,
447 maximum supported performance level (the highest supported `turbo
456 maximum supported performance level (the highest supported `turbo
465 inclusive) including both turbo and non-turbo P-states (see
466 `Turbo P-states Support`_).
477 Ratio of the `turbo range <turbo_>`_ size to the size of the entire
488 If set (equal to 1), the driver is not allowed to set any turbo P-states
489 (see `Turbo P-states Support`_). If unset (equal to 0, which is the
490 default), turbo P-states can be set by the driver.
509 is directly set to the highest non-turbo P-state or above it.
545 optimizations are done only in the turbo frequency range. Without it,
566 not allowed to use turbo P-states, so the maximum value of ``scaling_max_freq``
567 and ``scaling_min_freq`` is limited to the maximum non-turbo P-state frequency.
575 and ``scaling_min_freq`` corresponds to the maximum supported turbo P-state,
598 in the turbo frequency range.
705 `turbo range <turbo_>`_ is represented by one item in it (the topmost one). By
707 than the frequency of the highest non-turbo P-state listed by it, but the
709 returned for it matches the maximum supported turbo P-state (or is the
716 of the turbo range described above, this means that the maximum supported
718 of the highest supported non-turbo P-state listed by ``_PSS`` which, of course,
725 the turbo threshold if ``acpi-cpufreq`` is used as the scaling driver, because
726 in that case the turbo range corresponds to a small fraction of the frequency
728 the turbo range for the highest loads and the other loads above 50% that might
729 benefit from running at turbo frequencies will be given non-turbo P-states
734 turbo threshold. Namely, if that is not coordinated with the lists of P-states
736 a turbo P-state in those lists and there may be a problem with avoiding the
737 turbo range (if desirable or necessary). Usually, to avoid using turbo
739 by ``_PSS``, but that is not sufficient when there are other turbo P-states in