On Monday, March 20, 2017 08:58:40 AM Viresh Kumar wrote:
> On 19-03-17, 14:30, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > sugov_start() only initializes struct sugov_cpu per-CPU structures
> > for shared policies, but it should do that for
On Monday, March 20, 2017 08:58:40 AM Viresh Kumar wrote:
> On 19-03-17, 14:30, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > sugov_start() only initializes struct sugov_cpu per-CPU structures
> > for shared policies, but it should do that for single-CPU policies too.
> >
> >
On 19-03-17, 14:30, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> sugov_start() only initializes struct sugov_cpu per-CPU structures
> for shared policies, but it should do that for single-CPU policies too.
>
> That in particular makes the IO-wait boost
On 19-03-17, 14:30, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> sugov_start() only initializes struct sugov_cpu per-CPU structures
> for shared policies, but it should do that for single-CPU policies too.
>
> That in particular makes the IO-wait boost mechanism work in the
> cases
From: Rafael J. Wysocki
sugov_start() only initializes struct sugov_cpu per-CPU structures
for shared policies, but it should do that for single-CPU policies too.
That in particular makes the IO-wait boost mechanism work in the
cases when cpufreq policies correspond
From: Rafael J. Wysocki
sugov_start() only initializes struct sugov_cpu per-CPU structures
for shared policies, but it should do that for single-CPU policies too.
That in particular makes the IO-wait boost mechanism work in the
cases when cpufreq policies correspond to individual CPUs.
Fixes:
6 matches
Mail list logo