On 08-01-21, 09:44, Ionela Voinescu wrote: > Now that I think of it again (after spending 30 minutes trying to come > up with a more clear solution) I realised this is not actually a > problem :). > > The only location that checks the invariance status is schedutil, but > what a cpufreq governor does becomes irrelevant if you remove the > cpufreq driver.
Good catch :) > The only potential problem is if one then inmods a > cpufreq driver that's not invariant. But I think that might be on "if" > too many to consider. What do you think? Yeah, there is no need to worry about this then I think. I will resend the patches soon. -- viresh