Home
last modified time | relevance | path

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

12

/Linux-v5.10/Documentation/RCU/Design/Memory-Ordering/
DTree-RCU-Memory-Ordering.rst135 | the grace period won't expect quiescent states from them. Races |
384 quiescent states (or as described in a later section, had quiescent
386 non-idle CPUs report their own quiescent states, as shown in the
391 This is for the last CPU to report a quiescent state, which signals the
392 end of the grace period. Earlier quiescent states would push up the
394 that is waiting for additional quiescent states. However, ordering is
395 nevertheless preserved because some later quiescent state will acquire
425 If the CPU does a context switch, a quiescent state will be noted by
428 quiescent state will be noted by ``rcu_sched_clock_irq()`` on the right.
429 Either way, the passage through a quiescent state will be noted in a
[all …]
/Linux-v5.10/Documentation/RCU/Design/Expedited-Grace-Periods/
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-v5.10/Documentation/RCU/Design/Data-Structures/
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 quiescent-state information from the leaves to the root and also that
[all …]
/Linux-v5.10/Documentation/devicetree/bindings/regulator/
Dsprd,sc2731-regulator.txt3 The SC2731 integrates low-voltage and low quiescent current DCDC/LDO.
Dmax77802.txt61 3: Low Power which reduces the quiescent current down to only 1uA
/Linux-v5.10/Documentation/networking/
Dipvs-sysctl.rst156 persistent templates when the destination server is quiescent.
158 quiescent by setting its weight to 0 and it is desired that
161 connections are allowed to quiescent destination servers.
165 connection and the destination server is quiescent.
/Linux-v5.10/drivers/scsi/megaraid/
Dmegaraid_ioctl.h284 uint32_t quiescent; member
Dmega_common.h156 uint8_t quiescent; member
Dmegaraid_mm.c162 if (!adp->quiescent) { in mraid_mm_ioctl()
711 adp->quiescent = 0; in lld_ioctl()
920 adapter->quiescent = 1; in mraid_mm_register_adp()
Dmegaraid_mbox.c1877 if (adapter->quiescent) { in megaraid_mbox_runpendq()
2154 if (!adapter->quiescent) { in megaraid_isr()
3657 adapter->quiescent++; in wait_till_fw_empty()
3712 adapter->quiescent--; in megaraid_mbox_mm_done()
/Linux-v5.10/Documentation/admin-guide/cgroup-v1/
Dfreezer-subsystem.rst16 quiescent state. Once the tasks are quiescent another task can
/Linux-v5.10/Documentation/devicetree/bindings/mfd/
Drohm,bd70528-pmic.txt3 BD70528MWV is an ultra-low quiescent current general purpose, single-chip,
/Linux-v5.10/Documentation/RCU/
Dstallwarn.rst232 The "fqs=" shows the number of force-quiescent-state idle/offline
267 If all CPUs and tasks have passed through quiescent states, but the
276 of jiffies between force-quiescent-state scans, in this case three,
288 through the required quiescent states. The "g" number shows the current
Drcubarrier.rst333 since each CPU must undergo a context switch (or other quiescent
DRTFP.txt24 of "quiescent states" in the VM/XA hypervisor that are guaranteed not
548 Defines 'quiescent state'. Includes both measured and analytic
2510 Drives quiescent-state detection from RCU read-side primitives,
/Linux-v5.10/drivers/scsi/
Dmegaraid.c408 if (atomic_read(&adapter->quiescent) == 0) in megaraid_queue_lck()
1314 if(atomic_read(&adapter->quiescent) == 0) { in megaraid_isr_iomapped()
1394 if(atomic_read(&adapter->quiescent) == 0) { in megaraid_isr_memmapped()
2107 atomic_read(&adapter->quiescent)); in proc_show_config()
3801 atomic_set(&adapter->quiescent, 1); in mega_del_logdrv()
3828 atomic_set(&adapter->quiescent, 0); in mega_del_logdrv()
4110 if (atomic_read(&adapter->quiescent) == 0) in mega_internal_command()
4417 atomic_set(&adapter->quiescent, 0); in megaraid_probe_one()
Dmegaraid.h833 atomic_t quiescent; /* a stage reached when delete logical member
/Linux-v5.10/kernel/rcu/
DKconfig85 user-mode execution as quiescent states. Not for manual selection.
92 execution as quiescent states. It forces IPIs and context
/Linux-v5.10/kernel/time/
DKconfig148 userspace extended quiescent state and tickless cputime
/Linux-v5.10/tools/memory-model/Documentation/
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-v5.10/Documentation/virt/kvm/devices/
Darm-vgic-its.rst202 - The ITS is not enabled and quiescent
/Linux-v5.10/Documentation/admin-guide/
Dkernel-per-CPU-kthreads.rst213 CPUs to detect that it has passed through an RCU quiescent
216 the CPU in question has passed through a quiescent state.
/Linux-v5.10/Documentation/RCU/Design/Requirements/
DRequirements.rst611 | absolutely no code, RCU infers quiescent states only at special |
853 *quiescent state* for each thread, that is, a state in which RCU knows
1095 | sections because it is not legal to place a quiescent state (in this |
1439 to provide an RCU quiescent state. RCU also causes those CPUs'
1469 #. Forces immediate checking for quiescent states, rather than waiting
1769 itself is a quiescent state and thus a grace period, so the early-boot
2014 build, and if ``get_user()`` did page fault, the result would be a quiescent
2016 quiescent state could result in line 4 being a use-after-free access,
2183 through quiescent states at a reasonable frequency (preferably about
2187 If the gap between a successive pair of quiescent states grows too
[all …]
/Linux-v5.10/Documentation/scsi/
Dscsi_eh.rst151 Note that this does not mean lower layers are quiescent. If a LLDD
/Linux-v5.10/arch/
DKconfig614 that need it, such as userspace RCU extended quiescent state.

12