Re: [PATCH] cpufreq: schedutil: Update cached "current frequency" when limits change

2017-07-13 Thread Viresh Kumar
On 13-07-17, 18:52, Saravana Kannan wrote: > On 07/11/2017 10:24 PM, Viresh Kumar wrote: > >On 11-07-17, 19:24, Saravana Kannan wrote: > >>Currently, the governor calculates the next frequency, set the current CPU > >>frequency (policy->cur). It also assumes the current CPU frequency doesn't >

Re: [PATCH] cpufreq: schedutil: Update cached "current frequency" when limits change

2017-07-13 Thread Viresh Kumar
On 13-07-17, 18:52, Saravana Kannan wrote: > On 07/11/2017 10:24 PM, Viresh Kumar wrote: > >On 11-07-17, 19:24, Saravana Kannan wrote: > >>Currently, the governor calculates the next frequency, set the current CPU > >>frequency (policy->cur). It also assumes the current CPU frequency doesn't >

Re: [PATCH] cpufreq: schedutil: Update cached "current frequency" when limits change

2017-07-13 Thread Saravana Kannan
On 07/11/2017 10:24 PM, Viresh Kumar wrote: On 11-07-17, 19:24, Saravana Kannan wrote: Currently, the governor calculates the next frequency, set the current CPU frequency (policy->cur). It also assumes the current CPU frequency doesn't change if the next frequency isn't calculated again and

Re: [PATCH] cpufreq: schedutil: Update cached "current frequency" when limits change

2017-07-13 Thread Saravana Kannan
On 07/11/2017 10:24 PM, Viresh Kumar wrote: On 11-07-17, 19:24, Saravana Kannan wrote: Currently, the governor calculates the next frequency, set the current CPU frequency (policy->cur). It also assumes the current CPU frequency doesn't change if the next frequency isn't calculated again and

Re: [PATCH] cpufreq: schedutil: Update cached "current frequency" when limits change

2017-07-12 Thread Saravana Kannan
On 07/11/2017 10:24 PM, Viresh Kumar wrote: On 11-07-17, 19:24, Saravana Kannan wrote: Currently, the governor calculates the next frequency, set the current CPU frequency (policy->cur). It also assumes the current CPU frequency doesn't change if the next frequency isn't calculated again and

Re: [PATCH] cpufreq: schedutil: Update cached "current frequency" when limits change

2017-07-12 Thread Saravana Kannan
On 07/11/2017 10:24 PM, Viresh Kumar wrote: On 11-07-17, 19:24, Saravana Kannan wrote: Currently, the governor calculates the next frequency, set the current CPU frequency (policy->cur). It also assumes the current CPU frequency doesn't change if the next frequency isn't calculated again and

Re: [PATCH] cpufreq: schedutil: Update cached "current frequency" when limits change

2017-07-11 Thread Viresh Kumar
On 11-07-17, 19:24, Saravana Kannan wrote: > Currently, the governor calculates the next frequency, set the current CPU > frequency (policy->cur). It also assumes the current CPU frequency doesn't > change if the next frequency isn't calculated again and hence caches the > "current frequency". >

Re: [PATCH] cpufreq: schedutil: Update cached "current frequency" when limits change

2017-07-11 Thread Viresh Kumar
On 11-07-17, 19:24, Saravana Kannan wrote: > Currently, the governor calculates the next frequency, set the current CPU > frequency (policy->cur). It also assumes the current CPU frequency doesn't > change if the next frequency isn't calculated again and hence caches the > "current frequency". >