Lines Matching refs:quiescent

139 | happen, even if CPU 1 is in an RCU extended quiescent state           |
164 | the grace period won't expect quiescent states from them. Races       |
408 quiescent states (or as described in a later section, had quiescent
410 non-idle CPUs report their own quiescent states, as shown in the
415 This is for the last CPU to report a quiescent state, which signals the
416 end of the grace period. Earlier quiescent states would push up the
418 that is waiting for additional quiescent states. However, ordering is
419 nevertheless preserved because some later quiescent state will acquire
449 If the CPU does a context switch, a quiescent state will be noted by
452 quiescent state will be noted by ``rcu_sched_clock_irq()`` on the right.
453 Either way, the passage through a quiescent state will be noted in a
459 quiescent state, and invoke ``rcu_report_qs_rdp()``. If
460 ``rcu_report_qs_rdp()`` verifies that the quiescent state really does
467 only if the current CPU is reporting the last quiescent state for the
472 guarantees that the first CPU's quiescent state happens before the
474 repeatedly shows that all CPUs' quiescent states happen before the last
526 As noted above, idle and offline CPUs cannot report their own quiescent
528 reporting on their behalf. This process is called “forcing quiescent
534 Each pass of quiescent state forcing is guaranteed to traverse the leaf
535 ``rcu_node`` structures, and if there are no new quiescent states due to
539 quiescent state will be driven up towards the root. As with
540 self-reported quiescent states, the upwards driving stops once it
541 reaches an ``rcu_node`` structure that has quiescent states outstanding
584 | has reported its quiescent state, but it may be some milliseconds     |