On Wed, Nov 18, 2020 at 12:31:13PM +0800, Aubrey Li wrote: > Add idle cpumask to track idle cpus in sched domain. When a CPU > enters idle, if the idle driver indicates to stop tick, this CPU > is set in the idle cpumask to be a wakeup target. And if the CPU > is not in idle, the CPU is cleared in idle cpumask during scheduler > tick to ratelimit idle cpumask update.
So this will only have SIS consider CPUs that have the tick stopped? That might affect the facebook tail-latency workloads quite a bit.
