-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/22/2014 10:12 PM, Mike Galbraith wrote:
> On Wed, 2014-10-22 at 21:42 -0400, Rik van Riel wrote:
>> On 10/22/2014 07:20 PM, Mike Turquette wrote:
>>> On Wed, Oct 22, 2014 at 1:06 PM, Rik van Riel
>>> wrote: On 10/22/2014 02:07 AM, Mike Turquette
On Wed, 2014-10-22 at 21:42 -0400, Rik van Riel wrote:
> On 10/22/2014 07:20 PM, Mike Turquette wrote:
> > On Wed, Oct 22, 2014 at 1:06 PM, Rik van Riel
> > wrote: On 10/22/2014 02:07 AM, Mike Turquette wrote:
> arch_eval_cpu_freq and arch_scale_cpu_freq are added to allow
> the schedul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/22/2014 07:20 PM, Mike Turquette wrote:
> On Wed, Oct 22, 2014 at 1:06 PM, Rik van Riel
> wrote: On 10/22/2014 02:07 AM, Mike Turquette wrote:
arch_eval_cpu_freq and arch_scale_cpu_freq are added to allow
the scheduler to evaluate if c
On Wed, Oct 22, 2014 at 1:06 PM, Rik van Riel wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 10/22/2014 02:07 AM, Mike Turquette wrote:
>> arch_eval_cpu_freq and arch_scale_cpu_freq are added to allow the
>> scheduler to evaluate if cpu frequency should change and to invoke
>> tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/22/2014 02:07 AM, Mike Turquette wrote:
> arch_eval_cpu_freq and arch_scale_cpu_freq are added to allow the
> scheduler to evaluate if cpu frequency should change and to invoke
> that change from a safe context.
>
> They are weakly defined arch
arch_eval_cpu_freq and arch_scale_cpu_freq are added to allow the
scheduler to evaluate if cpu frequency should change and to invoke that
change from a safe context.
They are weakly defined arch functions that do nothing by default. A
CPUfreq governor could use these functions to implement a frequ
6 matches
Mail list logo