Re: [RFCv5 PATCH 43/46] sched/{fair,cpufreq_sched}: add reset_capacity interface

2015-10-12 Thread Steve Muckle
On 10/09/2015 02:14 AM, Juri Lelli wrote: >> Though I understand the initial stated motivation here (avoiding a >> > redundant capacity request upon idle entry), releasing the CPU's >> > capacity request altogether on idle seems like it could be a contentious >> > policy decision. >> > >> > An

Re: [RFCv5 PATCH 43/46] sched/{fair,cpufreq_sched}: add reset_capacity interface

2015-10-09 Thread Juri Lelli
Hi Steve, On 08/10/15 21:40, Steve Muckle wrote: > Hi Juri, > > On 07/07/2015 11:24 AM, Morten Rasmussen wrote: >> From: Juri Lelli >> >> When a CPU is going idle it is pointless to ask for an OPP update as we >> would wake up another task only to ask for the same capacity

Re: [RFCv5 PATCH 43/46] sched/{fair,cpufreq_sched}: add reset_capacity interface

2015-10-08 Thread Steve Muckle
Hi Juri, On 07/07/2015 11:24 AM, Morten Rasmussen wrote: > From: Juri Lelli > > When a CPU is going idle it is pointless to ask for an OPP update as we > would wake up another task only to ask for the same capacity we are already > running at (utilization gets moved to

[RFCv5 PATCH 43/46] sched/{fair,cpufreq_sched}: add reset_capacity interface

2015-07-07 Thread Morten Rasmussen
From: Juri Lelli juri.le...@arm.com When a CPU is going idle it is pointless to ask for an OPP update as we would wake up another task only to ask for the same capacity we are already running at (utilization gets moved to blocked_utilization). We thus add cpufreq_sched_reset_capacity() interface