Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux

Documentation: intel_pstate: Clarify coordination of P-State limits

Explain influence of per-core P-states and hyper threading on the
effective performance.

Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

authored by

Srinivas Pandruvada and committed by
Rafael J. Wysocki
60935c17 af3b7379

+9 -1
+9 -1
Documentation/admin-guide/pm/intel_pstate.rst
··· 495 495 496 496 2. Each individual CPU is affected by its own per-policy limits (that is, it 497 497 cannot be requested to run faster than its own per-policy maximum and it 498 - cannot be requested to run slower than its own per-policy minimum). 498 + cannot be requested to run slower than its own per-policy minimum). The 499 + effective performance depends on whether the platform supports per core 500 + P-states, hyper-threading is enabled and on current performance requests 501 + from other CPUs. When platform doesn't support per core P-states, the 502 + effective performance can be more than the policy limits set on a CPU, if 503 + other CPUs are requesting higher performance at that moment. Even with per 504 + core P-states support, when hyper-threading is enabled, if the sibling CPU 505 + is requesting higher performance, the other siblings will get higher 506 + performance than their policy limits. 499 507 500 508 3. The global and per-policy limits can be set independently. 501 509