On Fri, 2012-02-17 at 10:00 +0100, Dominik Brodowski wrote: > > Well, we can actually have both: Adding a new cpufreq governor "scheduler" > is easy. The scheduler stores the target frequency (in per-cent or > per-mille) in (per-cpu) data available to this governor, and kick a > (per-cpu?) thread which then handels the rest -- by existing cpufreq means. > The cpufreq part is easy, the sched part less so (I think). You might not have been reading what I wrote, kicking a kthread (or doing any other scheduler activity) from within the scheduler is way ugly and something I'd really rather avoid if at all possible. Yes I could do it, but I really really don't want to. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
