lkml.org 
[lkml]   [2017]   [Feb]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: 9908859acaa9 cpuidle/menu: add per CPU PM QoS resume latency consideration
From
Date


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

\
 
 \ /
  Last update: 2017-02-22 16:37    [W:0.374 / U:0.076 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site