| commit | aa439248ab71bcd2d26a01708dead4dd56616499 | |
| author | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | |
| Fri, 30 Dec 2016 14:56:14 +0000 (30 15:56 +0100) | ||
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | |
| Sat, 31 Dec 2016 20:48:42 +0000 (31 21:48 +0100) | ||
| tree | 2cb143137b8826ef2717f6a13e2ba43a62aeeb96 | treesnapshot (tar.gz zip) |
| parent | 366430b5c2f61a75d45b9fc00886ffff12f395ab | commitdiff |
cpufreq: intel_pstate: Use locking in intel_pstate_resume()
Theoretically, intel_pstate_resume() may be executed in parallel
with intel_pstate_set_policy(), if the latter is invoked via
cpufreq_update_policy() as a result of a notification, so use
intel_pstate_limits_lock in there too to avoid race conditions.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Theoretically, intel_pstate_resume() may be executed in parallel
with intel_pstate_set_policy(), if the latter is invoked via
cpufreq_update_policy() as a result of a notification, so use
intel_pstate_limits_lock in there too to avoid race conditions.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
| drivers/cpufreq/intel_pstate.c | diffblobblamehistory |