mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-08-26 10:49:33 +00:00
![]() At present, the value of timeout for freezing is 20s, which is meaningless in case that one thread is frozen with mutex locked and another thread is trying to lock the mutex, as this time of freezing will fail unavoidably. And if there is no new wakeup event registered, the system will waste at most 20s for such meaningless trying of freezing. With this patch, the value of timeout can be configured to smaller value, so such meaningless trying of freezing will be aborted in earlier time, and later freezing can be also triggered in earlier time. And more power will be saved. In normal case on mobile phone, it costs real little time to freeze processes. On some platform, it only costs about 20ms to freeze user space processes and 10ms to freeze kernel freezable threads. Signed-off-by: Liu Chuansheng <chuansheng.liu@intel.com> Signed-off-by: Li Fei <fei.li@intel.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> |
||
---|---|---|
.. | ||
regulator | ||
00-INDEX | ||
apm-acpi.txt | ||
basic-pm-debugging.txt | ||
charger-manager.txt | ||
devices.txt | ||
drivers-testing.txt | ||
freezing-of-tasks.txt | ||
interface.txt | ||
notifiers.txt | ||
opp.txt | ||
pci.txt | ||
pm_qos_interface.txt | ||
power_supply_class.txt | ||
runtime_pm.txt | ||
s2ram.txt | ||
states.txt | ||
suspend-and-cpuhotplug.txt | ||
swsusp-and-swap-files.txt | ||
swsusp-dmcrypt.txt | ||
swsusp.txt | ||
tricks.txt | ||
userland-swsusp.txt | ||
video.txt | ||
video_extension.txt |