On Wed, May 26, 2021 at 11:09 AM Jan Beulich wrote:
>
> On 26.05.2021 16:12, Jason Andryuk wrote:
> > On Wed, May 26, 2021 at 9:18 AM Jan Beulich wrote:
> >> Sorry, all quite nit-like remarks, but still ...
> >
> > It's fine. Would a design session be useful to discuss hwp?
>
> Is there anything
On 26.05.2021 16:12, Jason Andryuk wrote:
> On Wed, May 26, 2021 at 9:18 AM Jan Beulich wrote:
>> Sorry, all quite nit-like remarks, but still ...
>
> It's fine. Would a design session be useful to discuss hwp?
Is there anything beyond patch review that's necessary there? I'm
also not really se
On Wed, May 26, 2021 at 9:18 AM Jan Beulich wrote:
>
> On 03.05.2021 21:27, Jason Andryuk wrote:
> > For hwp, the standard governors are not usable, and only the internal
> > one is applicable.
>
> So you say "one" here but use plural in the subject. Which one is
> it (going to be)?
hwp only uses
On 03.05.2021 21:27, Jason Andryuk wrote:
> For hwp, the standard governors are not usable, and only the internal
> one is applicable.
So you say "one" here but use plural in the subject. Which one is
it (going to be)?
> Add the cpufreq_governor_internal boolean to
> indicate when an internal go
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-internal, will be used.
This is set during presmp_initcall, so that it can suppress governor
registration during initca