lkml.org 
[lkml]   [2018]   [Apr]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [PATCH v9 10/10] cpuidle: menu: Avoid selecting shallow states with stopped tick
On Thu, Apr 5, 2018 at 2:47 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> On Wed, Apr 04, 2018 at 10:50:36AM +0200, Rafael J. Wysocki wrote:
>> + if (tick_nohz_tick_stopped()) {
>> + /*
>> + * If the tick is already stopped, the cost of possible short
>> + * idle duration misprediction is much higher, because the CPU
>> + * may be stuck in a shallow idle state for a long time as a
>> + * result of it. In that case say we might mispredict and try
>> + * to force the CPU into a state for which we would have stopped
>> + * the tick, unless the tick timer is going to expire really
>> + * soon anyway.
>
> Wait what; the tick was stopped, therefore it _cannot_ expire soon.
>
> *confused*
>
> Did you mean s/tick/a/ ?

Yeah, that should be "a timer".

\
 
 \ /
  Last update: 2018-04-05 15:49    [W:0.049 / U:1.700 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site