Re: 9908859acaa9 cpuidle/menu: add per CPU PM QoS resume latency consideration
From: Peter Zijlstra
Date: Wed Feb 22 2017 - 08:12:28 EST
On Wed, Feb 22, 2017 at 01:56:37PM +0100, Mike Galbraith wrote:
> Do we really need a spinlock for that in the idle loop?
Urgh, that's broken on RT, you cannot schedule the idle loop.
Also, yeah, reading a s32 should not need no locking, but there's a
bunch of pointer chases in between :/
Nasty code that..