Lines Matching full:side

128  * srcu_read_lock_held - might we be in SRCU read-side critical section?
132 * read-side critical section. In absence of CONFIG_DEBUG_LOCK_ALLOC,
133 * this assumes we are in an SRCU read-side critical section unless it can
154 * srcu_lock_sync(), which is basically an empty *write*-side critical section,
194 * really are in an SRCU read-side critical section.
195 * @c: condition to check for update-side use
197 * If PROVE_RCU is enabled, invoking this outside of an RCU read-side
210 * really are in an SRCU read-side critical section.
213 * is enabled, invoking this outside of an RCU read-side critical
222 * really are in an SRCU read-side critical section.
230 * Enter an SRCU read-side critical section. Note that SRCU read-side
261 * Enter an SRCU read-side critical section, but for a light-weight
288 * Enter a semaphore-like SRCU read-side critical section, but for
306 * Enter an SRCU read-side critical section, but for a light-weight
333 * Enter an SRCU read-side critical section, but in an NMI-safe manner.
365 * Enter a semaphore-like SRCU read-side critical section. Note that
366 * SRCU read-side critical sections may be nested. However, it is
395 * Exit an SRCU read-side critical section.
411 * Exit a light-weight SRCU read-side critical section.
426 * Exit an SRCU read-side critical section, but not necessarily from
442 * Exit a light-weight SRCU read-side critical section.
458 * Exit an SRCU read-side critical section, but in an NMI-safe manner.
482 * Exit an SRCU read-side critical section, but not necessarily from