Re: [PATCH v4 01/15] cpufreq: Allow restricting to internal governors only

2023-06-15 Thread Jan Beulich
On 15.06.2023 16:04, Jason Andryuk wrote: > On Thu, Jun 15, 2023 at 9:21 AM Jan Beulich wrote: >> Yet then I find this approach a little odd anyway. I think the >> registration attempts would better be suppressed, thus also not >> resulting in (apparently) failed init-calls. Especially for the >>

Re: [PATCH v4 01/15] cpufreq: Allow restricting to internal governors only

2023-06-15 Thread Jason Andryuk
On Thu, Jun 15, 2023 at 9:21 AM Jan Beulich wrote: > > On 14.06.2023 20:02, Jason Andryuk wrote: > > @@ -121,6 +122,12 @@ int __init cpufreq_register_governor(struct > > cpufreq_governor *governor) > > if (!governor) > > return -EINVAL; > > > > +if (cpufreq_governor_internal &&

Re: [PATCH v4 01/15] cpufreq: Allow restricting to internal governors only

2023-06-15 Thread Jan Beulich
On 14.06.2023 20:02, Jason Andryuk wrote: > @@ -121,6 +122,12 @@ int __init cpufreq_register_governor(struct > cpufreq_governor *governor) > if (!governor) > return -EINVAL; > > +if (cpufreq_governor_internal && !governor->internal) > +return -EINVAL; > + > +if (!cp

[PATCH v4 01/15] cpufreq: Allow restricting to internal governors only

2023-06-14 Thread Jason Andryuk
For hwp, the standard governors are not usable, and only the internal one is applicable. Add the cpufreq_governor_internal boolean to indicate when an internal governor, like hwp, will be used. This is set during presmp_initcall, so that it can suppress governor registration during initcall. Add