Re: [PATCH] cpufreq: Rebuild sched-domains when removing cpufreq driver

[Pierre Gondois]

On 9/29/23 05:27, Viresh Kumar wrote:
> On 28-09-23, 14:49, Pierre Gondois wrote:
> > Another solution would be to call sched_cpufreq_governor_change()
> > from cpufreq_schedutil's init()/exit() callbacks. This would make
> > more sense as EAS/schedutil cpufreq are tightly bound, and it would
> > allow to cover all the possible paths.
> >
> > When tried locally, it seems to cover all scenarios:
> > - insmod/rmmod a cpufreq driver
> > - changing the governor policy
> > - offlining all the CPUs of a pd
>
> Right now it is done for all governors. We don't need that ? We just care about
> schedutil here ?

Yes exact, EAS requires the schedutil governor to be used by all policies. The purpose
of this function is to re-evaluate if EAS enablement conditions are met. I.e., if one
policy changed from/to schedutil, if EAS must be [de|re]activated.