Messages in this thread | | | Subject | Re: 9908859acaa9 cpuidle/menu: add per CPU PM QoS resume latency consideration | From | Alex Shi <> | Date | Wed, 22 Feb 2017 23:36:53 +0800 |
| |
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. >
Sorry. Mike. What you mean of 'took the zero added cycles option'? :)
Regards Alex
| |