Re: [PATCH v3 1/2] sched/cpufreq: always consider blocked FAIR utilization

2018-05-31 Thread Rafael J. Wysocki
On Wednesday, May 30, 2018 6:50:10 PM CEST Patrick Bellasi wrote: > On 27-May 11:50, Rafael J. Wysocki wrote: > > On Thu, May 24, 2018 at 4:10 PM, Patrick Bellasi > > wrote: > > > Since the refactoring introduced by: > > > > > >commit 8f111bc357aa ("cpufreq/schedutil: Rewrite CPUFREQ_RT

Re: [PATCH v3 1/2] sched/cpufreq: always consider blocked FAIR utilization

2018-05-31 Thread Rafael J. Wysocki
On Wednesday, May 30, 2018 6:50:10 PM CEST Patrick Bellasi wrote: > On 27-May 11:50, Rafael J. Wysocki wrote: > > On Thu, May 24, 2018 at 4:10 PM, Patrick Bellasi > > wrote: > > > Since the refactoring introduced by: > > > > > >commit 8f111bc357aa ("cpufreq/schedutil: Rewrite CPUFREQ_RT

Re: [PATCH v3 1/2] sched/cpufreq: always consider blocked FAIR utilization

2018-05-30 Thread Patrick Bellasi
On 27-May 11:50, Rafael J. Wysocki wrote: > On Thu, May 24, 2018 at 4:10 PM, Patrick Bellasi > wrote: > > Since the refactoring introduced by: > > > >commit 8f111bc357aa ("cpufreq/schedutil: Rewrite CPUFREQ_RT support") > > > > we aggregate FAIR utilization only if this class has runnable

Re: [PATCH v3 1/2] sched/cpufreq: always consider blocked FAIR utilization

2018-05-30 Thread Patrick Bellasi
On 27-May 11:50, Rafael J. Wysocki wrote: > On Thu, May 24, 2018 at 4:10 PM, Patrick Bellasi > wrote: > > Since the refactoring introduced by: > > > >commit 8f111bc357aa ("cpufreq/schedutil: Rewrite CPUFREQ_RT support") > > > > we aggregate FAIR utilization only if this class has runnable

Re: [PATCH v3 1/2] sched/cpufreq: always consider blocked FAIR utilization

2018-05-27 Thread Rafael J. Wysocki
On Thu, May 24, 2018 at 4:10 PM, Patrick Bellasi wrote: > Since the refactoring introduced by: > >commit 8f111bc357aa ("cpufreq/schedutil: Rewrite CPUFREQ_RT support") > > we aggregate FAIR utilization only if this class has runnable tasks. > This was mainly due to

Re: [PATCH v3 1/2] sched/cpufreq: always consider blocked FAIR utilization

2018-05-27 Thread Rafael J. Wysocki
On Thu, May 24, 2018 at 4:10 PM, Patrick Bellasi wrote: > Since the refactoring introduced by: > >commit 8f111bc357aa ("cpufreq/schedutil: Rewrite CPUFREQ_RT support") > > we aggregate FAIR utilization only if this class has runnable tasks. > This was mainly due to avoid the risk to stay on

[PATCH v3 1/2] sched/cpufreq: always consider blocked FAIR utilization

2018-05-24 Thread Patrick Bellasi
Since the refactoring introduced by: commit 8f111bc357aa ("cpufreq/schedutil: Rewrite CPUFREQ_RT support") we aggregate FAIR utilization only if this class has runnable tasks. This was mainly due to avoid the risk to stay on an high frequency just because of the blocked utilization of a CPU

[PATCH v3 1/2] sched/cpufreq: always consider blocked FAIR utilization

2018-05-24 Thread Patrick Bellasi
Since the refactoring introduced by: commit 8f111bc357aa ("cpufreq/schedutil: Rewrite CPUFREQ_RT support") we aggregate FAIR utilization only if this class has runnable tasks. This was mainly due to avoid the risk to stay on an high frequency just because of the blocked utilization of a CPU