On 22-03-17, 10:29, Peter Zijlstra wrote: > On Wed, Mar 22, 2017 at 01:56:53AM +0100, Rafael J. Wysocki wrote:
> > However, the same problem may occur for a cpufreq driver that doesn't > > support fast frequency switching and implements the ->target callback > > (that is, it doesn't use frequency tables), but trace_cpu_frequency() > > is not called if frequency updates are skipped in that case. > > I'm having trouble parsing that; am I right in understanding this is the > exact same scenario where only superfluous changes are omitted? Yes. Just for a different driver type. -- viresh
