Messages in this thread | | | Date | Wed, 26 Jul 2006 10:09:46 -0700 (PDT) | From | Linus Torvalds <> | Subject | Re: [patch] Reorganize the cpufreq cpu hotplug locking to not be totally bizare |
| |
On Wed, 26 Jul 2006, Dave Jones wrote: > > Looks sensible to me. Assuming it passes testing..
It looked sensible to me too, although it still shows some "Lukewarm IQ" notices for the ondemand driver:
Lukewarm IQ detected in hotplug locking BUG: warning at kernel/cpu.c:38/lock_cpu_hotplug() [<c0103d07>] show_trace+0xd/0x10 [<c01042ec>] dump_stack+0x19/0x1b [<c013778d>] lock_cpu_hotplug+0x43/0x69 [<c012f9df>] __create_workqueue+0x52/0x11f [<df0ec34b>] cpufreq_governor_dbs+0x9f/0x2bd [cpufreq_ondemand] [<c0305542>] __cpufreq_governor+0x57/0xd8 [<c0305700>] __cpufreq_set_policy+0x13d/0x1a9 [<c0305906>] store_scaling_governor+0x12d/0x155 [<c0304fbd>] store+0x34/0x45 [<c01998fc>] sysfs_write_file+0x99/0xbf [<c0164953>] vfs_write+0xab/0x157 [<c0164f8c>] sys_write+0x3b/0x60 [<c0102d41>] sysenter_past_esp+0x56/0x79
but is sure looks better than it used to. Which is why I already applied it ;)
Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |