summaryrefslogtreecommitdiff
path: root/bpfc
diff options
context:
space:
mode:
Diffstat (limited to 'bpfc')
0 files changed, 0 insertions, 0 deletions
tat only
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2016-06-27 23:47:15 +0200
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2016-06-27 23:47:15 +0200
commit5ab666e09541e64ce2fd73411c3b5b9e4ad334b1 (patch)
treea27fca471605ace51d24ee8a50619c9523e37250 /Documentation/men-chameleon-bus.txt
parent4c2e07c6a29e0129e975727b9f57eede813eea85 (diff)
intel_pstate: Do not clear utilization update hooks on policy changes
intel_pstate_set_policy() is invoked by the cpufreq core during driver initialization, on changes of policy attributes (minimim and maximum frequency, for example) via sysfs and via CPU notifications from the platform firmware. On some platforms the latter may occur relatively often. Commit bb6ab52f2bef (intel_pstate: Do not set utilization update hook too early) made intel_pstate_set_policy() clear the CPU's utilization update hook before updating the policy attributes for it (and set the hook again after doind that), but that involves invoking synchronize_sched() and adds overhead to the CPU notifications mentioned above and to the sched-RCU handling in general. That extra overhead is arguably not necessary, because updating policy attributes when the CPU's utilization update hook is active should not lead to any adverse effects, so drop the clearing of the hook from intel_pstate_set_policy() and make it check if the hook has been set already when attempting to set it. Fixes: bb6ab52f2bef (intel_pstate: Do not set utilization update hook too early) Reported-by: Jisheng Zhang <jszhang@marvell.com> Tested-by: Jisheng Zhang <jszhang@marvell.com> Tested-by: Doug Smythies <dsmythies@telus.net> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'Documentation/men-chameleon-bus.txt')