summaryrefslogtreecommitdiffstats
path: root/drivers/acpi/acpica
diff options
context:
space:
mode:
authorAndi Kleen <andi@firstfloor.org>2012-02-06 08:17:11 -0800
committerLen Brown <len.brown@intel.com>2012-03-22 02:16:14 -0400
commit2815ab92ba3ab27556212cc306288dc95692824b (patch)
tree5e18864dbc2f07f7da0f552ea5e4c2624d7a8fdb /drivers/acpi/acpica
parentc16fa4f2ad19908a47c63d8fa436a1178438c7e7 (diff)
downloadlinux-2815ab92ba3ab27556212cc306288dc95692824b.tar.bz2
ACPI: Do cpufreq clamping for throttling per package v2
On Intel CPUs the processor typically uses the highest frequency set by any logical CPU. When the system overheats Linux first forces the frequency to the lowest available one to lower the temperature. However this was done only per logical CPU, which means all logical CPUs in a package would need to go through this before the frequency is actually lowered. Worse this delay actually prevents real throttling, because the real throttle code only proceeds when the lowest frequency is already reached. So when a throttle event happens force the lowest frequency for all CPUs in the package where it happened. The per CPU state is now kept per package, not per logical CPU. An alternative would be to do it per cpufreq unit, but since we want to bring down the temperature of the complete chip it's better to do it for all. In principle it may even make sense to do it for all CPUs, but I kept it on the package for now. With this change the frequency is actually lowered, which in terms also allows real throttling to proceed. I also removed an unnecessary per cpu variable initialization. v2: Fix package mapping Cc: <stable@vger.kernel.org> Signed-off-by: Andi Kleen <ak@linux.intel.com> Signed-off-by: Len Brown <len.brown@intel.com>
Diffstat (limited to 'drivers/acpi/acpica')
0 files changed, 0 insertions, 0 deletions