lkml.org 
[lkml]   [2012]   [Nov]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [RFC PATCH] Fix abnormal rcu dynticks_nesting values related to async page fault
From
2012/11/27 Paul E. McKenney <paulmck@linux.vnet.ibm.com>:
> It is OK to call rcu_irq_exit() without a matching rcu_irq_enter() -only-
> if you have also called rcu_idle_exit() since the last rcu_idle_enter().
> There will be a similar rule for rcu_user_exit().
>
> More generally, it is OK to call rcu_irq_exit() without a matching
> rcu_irq_enter() only if RCU believes that the CPU you are running on is
> non-idle.

Perfect!

> On 32-bit systems, you are only allowed a few tens of million
> such unmatched rcu_irq_enter() calls in a given RCU-non-idle region.
>
> All courtesy of RCU's need to tolerate architectures that enter
> interrupt handlers without ever leaving them and vice versa. ;-)

RCU idle mode in a hostile environment ;-)


\
 
 \ /
  Last update: 2012-11-27 18:21    [W:0.116 / U:0.936 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site