summaryrefslogtreecommitdiffstats
path: root/Documentation/cpu-freq/user-guide.txt
diff options
context:
space:
mode:
authorDarrick J. Wong <djwong@us.ibm.com>2008-04-18 22:31:12 +0200
committerDave Jones <davej@redhat.com>2008-04-28 22:27:08 +0200
commite8628dd06d66f2e3965ec9742029b401d63434f1 (patch)
tree341d5a2e36c877bd52c5567aa5791557a6920557 /Documentation/cpu-freq/user-guide.txt
parent[CPUFREQ] Make acpi-cpufreq more robust against BIOS freq changes behind our ... (diff)
downloadlinux-e8628dd06d66f2e3965ec9742029b401d63434f1.tar.xz
linux-e8628dd06d66f2e3965ec9742029b401d63434f1.zip
[CPUFREQ] expose cpufreq coordination requirements regardless of coordination mechanism
Currently, affected_cpus shows which CPUs need to have their frequency coordinated in software. When hardware coordination is in use, the contents of this file appear the same as when no coordination is required. This can lead to some confusion among user-space programs, for example, that do not know that extra coordination is required to force a CPU core to a particular speed to control power consumption. To fix this, create a "related_cpus" attribute that always displays the coordination map regardless of whatever coordination strategy the cpufreq driver uses (sw or hw). If the cpufreq driver does not provide a value, fall back to policy->cpus. Signed-off-by: Darrick J. Wong <djwong@us.ibm.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Dave Jones <davej@redhat.com>
Diffstat (limited to 'Documentation/cpu-freq/user-guide.txt')
0 files changed, 0 insertions, 0 deletions