Re: [PATCH v2 2/3] cpufreq: intel_pstate: Do not reinit performance limits in ->setpolicy

2017-03-02 Thread Rafael J. Wysocki
On Wed, Mar 1, 2017 at 12:09 AM, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > If the current P-state selection algorithm is set to "performance" > in intel_pstate_set_policy(), the limits may be initialized from > scratch, but only if no_turbo is not set and the maximum frequency > allo

Re: [PATCH v2 2/3] cpufreq: intel_pstate: Do not reinit performance limits in ->setpolicy

2017-03-02 Thread Rafael J. Wysocki
On Thu, Mar 2, 2017 at 6:18 PM, Rafael J. Wysocki wrote: > On Wed, Mar 1, 2017 at 12:09 AM, Rafael J. Wysocki wrote: >> From: Rafael J. Wysocki >> >> If the current P-state selection algorithm is set to "performance" >> in intel_pstate_set_policy(), the limits may be initialized from >> scratch,

[PATCH v2 2/3] cpufreq: intel_pstate: Do not reinit performance limits in ->setpolicy

2017-02-28 Thread Rafael J. Wysocki
From: Rafael J. Wysocki If the current P-state selection algorithm is set to "performance" in intel_pstate_set_policy(), the limits may be initialized from scratch, but only if no_turbo is not set and the maximum frequency allowed for the given CPU (i.e. the policy object representing it) is at l