On Thu, Jul 20, 2017 at 9:09 PM, Viresh Kumar <viresh.ku...@linaro.org> wrote: > On 20-07-17, 12:49, Joel Fernandes wrote: >> Yes I think that's fine, I thought about it some more and I think this >> can be an issue in a scenario where >> >> iowait_boost_max < policy->min but:
Uhh I meant to say here iowait_boost < policy->min. Sorry. > We will never have this case as boost-max is set to cpuinfo.max_freq. But you're right it can't be an issue in current code. I was just thinking of future proofing it incase someone decided to lower the boost-max in the code for whatever reason and forgets to handle this. thanks, -Joel
