_______________________________________ From: cpufreq-owner@xxxxxxxxxxxxxxx [cpufreq-owner@xxxxxxxxxxxxxxx] On Behalf Of Thomas Renninger [trenn@xxxxxxx] > Beside powersaving there may also be a performance issue with the > deferred timer approach. When the cpu is woken up, there may be > CPU intensive work to do. But the cpufreq subsystem would lower > frequency because it only knows about the history and does not know > that a task is scheduled on this CPU now... That can definitely be a problem on Arm, and it's worse if the sampling rate is relatively slow, because if you get taken to a low frequency coming out of idle then you'll stay there for the full duration of the sample. I have observed this. Haven't come up with the perfect solution yet, though...but it's the exact opposite of what you want. sf -- 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
