Re: 9908859acaa9 cpuidle/menu: add per CPU PM QoS resume latency consideration
From: Alex Shi
Date: Wed Feb 22 2017 - 10:37:31 EST
On 02/22/2017 11:03 PM, Mike Galbraith wrote:
>> > Yes, the dev_pm_qos_read_value() using a power.lock, that is right for normal device.
>> > But as to this cpu here, the lock isn't necessary.
>> > Hi Rafael,
>> > Is this fix ok?
> That's what I was gonna do, but then figured RT users will take full
> control when it really matters, so took the zero added cycles option
> for RT instead.
What you mean of 'took the zero added cycles option'? :)