Hosts the 0x221E linux distro kernel. https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.6.y 2012-07-26T04:03:58Z 2012-07-26T04:03:58Z Len Brown 2012-07-26T04:03:58Z urn:sha1:ec033d0a02901551346b9f43f8ff9bad51378891 2012-07-14T15:42:56Z Len Brown 2012-06-14T02:12:51Z urn:sha1:fa7584e13ac8e6a306085bba0a931f3135f1d8c4 In an effort to be fair to bound processes, acpi_pad periodically moves its forced-idle threads. The default interval for moving the threads is 10 seconds. Measurements show that reducing this to 1 second has no power or performance impact, so reduce default to 1 second. Signed-off-by: Len Brown <len.brown@intel.com> 2012-06-30T04:51:13Z Stuart Hayes 2012-06-13T21:10:45Z urn:sha1:5f1601261050251a5ca293378b492a69d590dacb The acpi_pad driver can get stuck in destroy_power_saving_task() waiting for kthread_stop() to stop a power_saving thread. The problem is that the isolated_cpus_lock mutex is owned when destroy_power_saving_task() calls kthread_stop(), which waits for a power_saving thread to end, and the power_saving thread tries to acquire the isolated_cpus_lock when it calls round_robin_cpu(). This patch fixes the issue by making round_robin_cpu() use its own mutex. https://bugzilla.kernel.org/show_bug.cgi?id=42981 Cc: stable@vger.kernel.org Signed-off-by: Stuart Hayes <Stuart_Hayes@Dell.com> Signed-off-by: Len Brown <len.brown@intel.com> 2012-06-14T02:07:20Z Len Brown 2012-06-14T02:07:20Z urn:sha1:150ed86fade791d82319b27e84a7a6d2de84d1fa "acpi_pad/%d" is a better thread name than generic "power_saving/%d" because users who see these threads will know the name of the driver that caused them. Signed-off-by: Len Brown <len.brown@intel.com> 2011-03-23T05:36:45Z Naga Chumbalkar 2011-02-02T23:27:04Z urn:sha1:cdf2a4eeded69f66ec8c5098c375fe49e0820127 Minor format change. Signed-off-by: Naga Chumbalkar <nagananda.chumbalkar@hp.com> Signed-off-by: Len Brown <len.brown@intel.com> 2011-03-23T05:34:15Z Naga Chumbalkar 2011-02-02T23:26:58Z urn:sha1:32297abd90a5d181e8e026c8b8e65ef41e9ffc07 Make /sys output from acpi_pad more readable. Before the fix: # cat idlecpus idlepct rrtime 00000000510 After the fix: # cat idlecpus idlepct rrtime 00000000 5 10 Signed-off-by: Naga Chumbalkar <nagananda.chumbalkar@hp.com> Signed-off-by: Len Brown <len.brown@intel.com> 2010-10-21T20:45:38Z Linus Torvalds 2010-10-21T20:45:38Z urn:sha1:2a8b67fb72c4c4bc15fe8095e3ed613789c8b82f * 'x86-idle-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip: x86, hotplug: In the MWAIT case of play_dead, CLFLUSH the cache line x86, hotplug: Move WBINVD back outside the play_dead loop x86, hotplug: Use mwait to offline a processor, fix the legacy case x86, mwait: Move mwait constants to a common header file 2010-09-29T18:08:10Z Len Brown 2010-09-28T20:50:50Z urn:sha1:c9ad8e062e4c733b36fc10ebc201bedde1a4da80 acpi_pad.c:432: warning: ‘num_cpus’ may be used uninitialized in this function gcc 4.4.4 was unable to notice that num_cpus is always set. Re-arrange the code to un-confuse gcc, and also make it easier for humans to read.... Signed-off-by: Len Brown <len.browns@intel.com> 2010-09-17T22:36:40Z H. Peter Anvin 2010-09-17T22:36:40Z urn:sha1:bc83cccc761953f878088cdfa682de0970b5561f We have MWAIT constants spread across three different .c files, for no good reason. Move them all into a common header file. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com> Reviewed-by: Arjan van de Ven <arjan@linux.intel.com> Cc: Len Brown <lenb@kernel.org> LKML-Reference: <tip-*@git.kernel.org> 2010-07-27T10:40:54Z John Stultz 2010-07-14T00:56:20Z urn:sha1:592913ecb87a9e06f98ddb55b298f1a66bf94c6b Now that all arches have been converted over to use generic time via clocksources or arch_gettimeoffset(), we can remove the GENERIC_TIME config option and simplify the generic code. Signed-off-by: John Stultz <johnstul@us.ibm.com> LKML-Reference: <1279068988-21864-4-git-send-email-johnstul@us.ibm.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>