The menu governor tries to deduce the next wakeup but based on events per cpu. That means if a task with a specific behavior is migrated across cpus, the statistics will be wrong.
btw this is largely a misunderstanding; tasks are not the issue; tasks use timers and those are perfectly predictable. It's interrupts that are not and the heuristics are for that. Now, if your hardware does the really-bad-for-power wake-all on any interrupt, then the menu governor logic is not good for you; rather than looking at the next timer on the current cpu you need to look at the earliest timer on the set of bundled cpus as the upper bound of the next wake event. And maybe even more special casing is needed... but I doubt it. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
