Home
last modified time | relevance | path

Searched refs:quiescent (Results 1 – 18 of 18) sorted by relevance

/linux/drivers/md/dm-vdo/
H A Dadmin-state.c70 .quiescent = true,
98 .quiescent = true,
123 .quiescent = true,
135 .quiescent = true,
340 if (code->quiescent) { in vdo_start_draining()
H A Dadmin-state.h23 bool quiescent; member
136 return vdo_get_admin_state_code(state)->quiescent; in vdo_is_state_quiescent()
/linux/Documentation/RCU/Design/Memory-Ordering/
H A DTree-RCU-Memory-Ordering.rst139 | 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.
[all …]
/linux/Documentation/RCU/Design/Expedited-Grace-Periods/
H A DExpedited-Grace-Periods.rst22 has not yet provided a quiescent state for the current expedited
29 a faster quiescent state where possible, and triggering a report
30 of that quiescent state.
31 As always for RCU, once everything has spent some time in a quiescent
53 in quiescent states.
61 If not, the handler can immediately report a quiescent state.
63 invocation will provide the needed quiescent-state report.
74 The CPU will report a quiescent state just after enqueuing the task because
123 quiescent states. However, because the ``rcu_read_lock_sched()`` and
129 then ``rcu_exp_handler()`` reports the quiescent state.
[all …]
/linux/Documentation/RCU/Design/Data-Structures/
H A DData-Structures.rst39 such as quiescent states, dyntick-idle transitions,
50 has passed through a quiescent state.
104 the last CPU to report a quiescent state into a given ``rcu_node``
112 there are in the system, at most 64 quiescent-state reports per grace
158 grace-period state, and maintains state used to force quiescent
161 quiescent-state information from the leaves to the root, and also
173 #. ``rcu_data``: This per-CPU structure is the focus of quiescent-state
176 more-efficient propagation of quiescent states up the ``rcu_node``
199 and maintains state used to force quiescent states when grace periods
311 | needs to report quiescent state (no qsmask), update rdp->gp_seq, |
[all …]
/linux/fs/resctrl/
H A DKconfig19 controls and monitors are left in a quiescent, permissive state.
/linux/drivers/scsi/megaraid/
H A Dmegaraid_ioctl.h284 uint32_t quiescent; member
H A Dmega_common.h156 uint8_t quiescent; member
/linux/tools/testing/selftests/sched_ext/
H A Dmaximal.bpf.c146 .quiescent = (void *) maximal_quiescent,
/linux/drivers/scsi/
H A Dmegaraid.c406 if (atomic_read(&adapter->quiescent) == 0) in megaraid_queue_lck()
1313 if(atomic_read(&adapter->quiescent) == 0) { in megaraid_isr_iomapped()
1393 if(atomic_read(&adapter->quiescent) == 0) { in megaraid_isr_memmapped()
2090 atomic_read(&adapter->quiescent)); in proc_show_config()
3774 atomic_set(&adapter->quiescent, 1); in mega_del_logdrv()
3801 atomic_set(&adapter->quiescent, 0); in mega_del_logdrv()
4079 if (atomic_read(&adapter->quiescent) == 0) in mega_internal_command()
4384 atomic_set(&adapter->quiescent, 0); in megaraid_probe_one()
/linux/Documentation/RCU/Design/Requirements/
H A DRequirements.rst612 | absolutely no code, RCU infers quiescent states only at special |
854 *quiescent state* for each thread, that is, a state in which RCU knows
1096 | sections because it is not legal to place a quiescent state (in this |
1440 to provide an RCU quiescent state. RCU also causes those CPUs'
1470 #. Forces immediate checking for quiescent states, rather than waiting
1769 itself is a quiescent state and thus a grace period, so the early-boot
1950 and also by reporting quiescent states explicitly when a CPU goes
1951 offline. This explicit reporting of quiescent states avoids any need
1952 for the force-quiescent-state loop (FQS) to report quiescent states for
1956 An offline CPU's quiescent state will be reported either:
[all …]
/linux/kernel/sched/ext/
H A Dinternal.h494 void (*quiescent)(struct task_struct *p, u64 deq_flags); member
1052 void (*quiescent)(struct task_struct *p, u64 deq_flags); member
H A Dext.c2302 if (SCX_HAS_OP(sch, quiescent) && !task_on_rq_migrating(p)) in dequeue_task_scx()
2303 SCX_CALL_OP_TASK(sch, quiescent, rq, p, deq_flags); in dequeue_task_scx()
8268 .quiescent = sched_ext_ops__quiescent,
8335 .quiescent = sched_ext_ops__quiescent,
10930 CID_OFFSET_MATCH(quiescent, quiescent); in scx_init()
/linux/tools/memory-model/Documentation/
H A Dsimple.txt126 data sets. For example, each CPU does private quiescent-state processing
128 locking to report quiescent states up the grace-period combining tree.
/linux/kernel/rcu/
H A DKconfig98 idle, and user-mode execution as quiescent states. Not for
118 user-mode execution as quiescent states. It forces IPIs and
/linux/Documentation/scheduler/
H A Dsched-ext.rst453 ops.quiescent();
479 ops.quiescent(); /* Task releases its assigned CPU (wait) */
499 ``ops.stopping()`` -> ``ops.quiescent()`` -> (property change callback) ->
/linux/tools/sched_ext/
H A Dscx_flatcg.bpf.c969 .quiescent = (void *)fcg_quiescent,
/linux/Documentation/scsi/
H A Dscsi_eh.rst152 Note that this does not mean lower layers are quiescent. If a LLDD