Lines Matching full:critical

83  * srcu_read_lock_held - might we be in SRCU read-side critical section?
87  * read-side critical section.  In absence of CONFIG_DEBUG_LOCK_ALLOC,
88  * this assumes we are in an SRCU read-side critical section unless it can
109  * srcu_lock_sync(), which is basically an empty *write*-side critical section,
160  *	really are in an SRCU read-side critical section.
164  * critical section will result in an RCU-lockdep splat, unless @c evaluates
176  *	really are in an SRCU read-side critical section.
179  * is enabled, invoking this outside of an RCU read-side critical
188  *	really are in an SRCU read-side critical section.
196  * Enter an SRCU read-side critical section.  Note that SRCU read-side
197  * critical sections may be nested.  However, it is illegal to
223  * Enter an SRCU read-side critical section, but in an NMI-safe manner.
251  * Enter a semaphore-like SRCU read-side critical section.  Note that
252  * SRCU read-side critical sections may be nested.  However, it is
280  * Exit an SRCU read-side critical section.
296  * Exit an SRCU read-side critical section, but in an NMI-safe manner.
320  * Exit an SRCU read-side critical section, but not necessarily from