Thanks for immediate response Viresh. On Mon, Sep 16, 2013 at 1:46 AM, Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote: > What's the problem you see in OS doing that? Its not about the guarantee > that OS can change freq in that time, but is more about hardware... And > so it doesn't matter who changes it.. Yeah actually that is what my concern is. It seems that for changing the frequency we need to acquire a lock (in cpufreq_driver_target()). Hence even though the hardware is capable of ns level DVFS, OS overhead may be large enough to take advantage of it. Can we measure this overhead? > Ya, the API is open to be called from anywhere you want... but then its > your hardware and you must know what you are doing :) Great to know. Thanks!! -- 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
