30 Jun
2017
30 Jun
'17
3:27 a.m.
On 29-06-17, 14:23, Srinivas Pandruvada wrote:
On Thu, 2017-06-29 at 10:56 +0530, Viresh Kumar wrote:
From: Steve Muckle smuckle.linux@gmail.com
In preparation for the scheduler cpufreq callback happening on remote CPUs, check for this case in intel_pstate which currently requires the callback run on the local CPU. Such callbacks are ignored for now.
Is it possible that we miss a chance to calculate load periodically at a predefined interval (10ms default), because the callback happened on a different CPU?
We aren't updating cpu->sample.time for remote callbacks here, so no we shouldn't miss anything.
-- viresh