On vrijdag 6 augustus 2021 16:07:18 CEST Diederik de Haas wrote: > > > -CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y > > > +# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set > > > -# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set > > > +CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y > > > -CONFIG_CPU_FREQ_GOV_ONDEMAND=m > > > +CONFIG_CPU_FREQ_GOV_ONDEMAND=y > > > > Hmm, CONFIG_CPU_FREQ_GOV_ONDEMAND=m is already there, so you should be > > able to switch to that if you prefer it?! > > Yes, afaik it isn't needed. > I did notice that there are 2 schedulers which are often used as default, > namely 'performance' and 'schedutil' and those are also builtin. > That's the reason I made 'ondemand' builtin as well, but it's entirely > possible that correlation != causation and I inferred > an incorrect 'conclusion'. > > Trying to find why 'performance' and 'schedutil' were builtin, resulted in > https://salsa.debian.org/kernel-team/linux/-/commit/e5b976c268e44d452bc5ae23 > b765eab26c4409ae which suggest the (sole) reason that it got builtin is that > it couldn't be modular in 4.9. That can very well have changed since. If you do 'make menuconfig' and change the default governor, it automatically makes the matching CPU_FREQ_GOV_* parameter builtin. And you can't change that. And apparently you can't make CPU_FREQ_GOV_PERFORMANCE a module. At all. So menuconfig is telling me that the default governor must use a builtin module.
Attachment:
signature.asc
Description: This is a digitally signed message part.