Re: [RFC PATCH] sched: idle: Introduce CPU-specific idle=poll

[Peter Zijlstra]

On Sat, Jun 21, 2025 at 07:57:45PM -0400, Aaron Tomlin wrote:
> Currently, the idle=poll kernel boot parameter applies globally, forcing
> all CPUs into a shallow polling idle state to ensure ultra-low latency
> responsiveness. While this is beneficial for extremely latency-sensitive
> workloads, this global application lacks flexibility and can lead to
> significant power inefficiency. This is particularly evident in systems
> with a high CPU count, such as those utilising the
> Full Dynticks/Adaptive Tick feature (i.e., nohz_full). In such
> environments, only a subset of CPUs might genuinely require
> sub-microsecond responsiveness, while others, though active, could
> benefit from entering deeper idle states to conserve power.

Can't we already do this at runtime with pmqos? If you set your latency
demand very low, it should end up picking the poll state, no? And you
can do this per-cpu.