Re: [PATCH 3/3] cpufreq: intel_pstate: Provide resolve_freq() to fix regression

2017-06-11 Thread Viresh Kumar
On 10-06-17, 02:26, Joel Fernandes wrote: > On Fri, Jun 9, 2017 at 3:15 AM, Viresh Kumar wrote: > > When the schedutil governor calls cpufreq_driver_resolve_freq() for the > > intel_pstate (in passive mode) driver, it simply returns the requested > > frequency as there is

Re: [PATCH 3/3] cpufreq: intel_pstate: Provide resolve_freq() to fix regression

2017-06-11 Thread Viresh Kumar
On 10-06-17, 02:26, Joel Fernandes wrote: > On Fri, Jun 9, 2017 at 3:15 AM, Viresh Kumar wrote: > > When the schedutil governor calls cpufreq_driver_resolve_freq() for the > > intel_pstate (in passive mode) driver, it simply returns the requested > > frequency as there is no ->resolve_freq()

Re: [PATCH 3/3] cpufreq: intel_pstate: Provide resolve_freq() to fix regression

2017-06-10 Thread Joel Fernandes
On Fri, Jun 9, 2017 at 3:15 AM, Viresh Kumar wrote: > When the schedutil governor calls cpufreq_driver_resolve_freq() for the > intel_pstate (in passive mode) driver, it simply returns the requested > frequency as there is no ->resolve_freq() callback provided. > > The

Re: [PATCH 3/3] cpufreq: intel_pstate: Provide resolve_freq() to fix regression

2017-06-10 Thread Joel Fernandes
On Fri, Jun 9, 2017 at 3:15 AM, Viresh Kumar wrote: > When the schedutil governor calls cpufreq_driver_resolve_freq() for the > intel_pstate (in passive mode) driver, it simply returns the requested > frequency as there is no ->resolve_freq() callback provided. > > The result is that

[PATCH 3/3] cpufreq: intel_pstate: Provide resolve_freq() to fix regression

2017-06-09 Thread Viresh Kumar
When the schedutil governor calls cpufreq_driver_resolve_freq() for the intel_pstate (in passive mode) driver, it simply returns the requested frequency as there is no ->resolve_freq() callback provided. The result is that get_next_freq() doesn't get a chance to know the frequency which will be

[PATCH 3/3] cpufreq: intel_pstate: Provide resolve_freq() to fix regression

2017-06-09 Thread Viresh Kumar
When the schedutil governor calls cpufreq_driver_resolve_freq() for the intel_pstate (in passive mode) driver, it simply returns the requested frequency as there is no ->resolve_freq() callback provided. The result is that get_next_freq() doesn't get a chance to know the frequency which will be