| /linux-5.19.10/Documentation/RCU/Design/Memory-Ordering/ |
| D | Tree-RCU-Memory-Ordering.rst | 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.
[all …]
|
| /linux-5.19.10/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| D | Expedited-Grace-Periods.rst | 22 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-5.19.10/Documentation/RCU/Design/Data-Structures/ |
| D | Data-Structures.rst | 39 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-5.19.10/Documentation/devicetree/bindings/regulator/ |
| D | sprd,sc2731-regulator.txt | 3 The SC2731 integrates low-voltage and low quiescent current DCDC/LDO.
|
| D | maxim,max77802.yaml | 27 3 - Low Power which reduces the quiescent current down to only 1uA
|
| /linux-5.19.10/drivers/scsi/megaraid/ |
| D | megaraid_ioctl.h | 284 uint32_t quiescent; member
|
| D | mega_common.h | 156 uint8_t quiescent; member
|
| D | megaraid_mm.c | 162 if (!adp->quiescent) { in mraid_mm_ioctl()
715 adp->quiescent = 0; in lld_ioctl()
929 adapter->quiescent = 1; in mraid_mm_register_adp()
|
| D | megaraid_mbox.c | 1875 if (adapter->quiescent) { in megaraid_mbox_runpendq()
2152 if (!adapter->quiescent) { in megaraid_isr()
3648 adapter->quiescent++; in wait_till_fw_empty()
3703 adapter->quiescent--; in megaraid_mbox_mm_done()
|
| /linux-5.19.10/Documentation/networking/ |
| D | ipvs-sysctl.rst | 155 persistent templates when the destination server is quiescent.
157 quiescent by setting its weight to 0 and it is desired that
160 connections are allowed to quiescent destination servers.
164 connection and the destination server is quiescent.
|
| /linux-5.19.10/Documentation/admin-guide/cgroup-v1/ |
| D | freezer-subsystem.rst | 16 quiescent state. Once the tasks are quiescent another task can
|
| /linux-5.19.10/drivers/scsi/ |
| D | megaraid.c | 406 if (atomic_read(&adapter->quiescent) == 0) in megaraid_queue_lck()
1312 if(atomic_read(&adapter->quiescent) == 0) { in megaraid_isr_iomapped()
1392 if(atomic_read(&adapter->quiescent) == 0) { in megaraid_isr_memmapped()
2093 atomic_read(&adapter->quiescent)); in proc_show_config()
3777 atomic_set(&adapter->quiescent, 1); in mega_del_logdrv()
3804 atomic_set(&adapter->quiescent, 0); in mega_del_logdrv()
4082 if (atomic_read(&adapter->quiescent) == 0) in mega_internal_command()
4390 atomic_set(&adapter->quiescent, 0); in megaraid_probe_one()
|
| D | megaraid.h | 854 atomic_t quiescent; /* a stage reached when delete logical member
|
| /linux-5.19.10/kernel/rcu/ |
| D | Kconfig | 88 idle, and user-mode execution as quiescent states. Not for
104 user-mode execution as quiescent states. It forces IPIs and
|
| /linux-5.19.10/Documentation/RCU/ |
| D | stallwarn.rst | 266 The "fqs=" shows the number of force-quiescent-state idle/offline
290 If all CPUs and tasks have passed through quiescent states, but the
299 of jiffies between force-quiescent-state scans, in this case three,
312 through the required quiescent states. The "g" number shows the current
|
| D | rcubarrier.rst | 333 since each CPU must undergo a context switch (or other quiescent
|
| D | RTFP.txt | 24 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-5.19.10/Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 612 | 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-5.19.10/kernel/time/ |
| D | Kconfig | 158 userspace extended quiescent state and tickless cputime
|
| /linux-5.19.10/tools/memory-model/Documentation/ |
| D | simple.txt | 126 data sets. For example, each CPU does private quiescent-state processing
128 locking to report quiescent states up the grace-period combining tree.
|
| /linux-5.19.10/Documentation/admin-guide/ |
| D | kernel-per-CPU-kthreads.rst | 213 CPUs to detect that it has passed through an RCU quiescent
216 the CPU in question has passed through a quiescent state.
|
| /linux-5.19.10/Documentation/virt/kvm/devices/ |
| D | arm-vgic-its.rst | 202 - The ITS is not enabled and quiescent
|
| /linux-5.19.10/Documentation/scsi/ |
| D | scsi_eh.rst | 150 Note that this does not mean lower layers are quiescent. If a LLDD
|
| /linux-5.19.10/Documentation/driver-api/ |
| D | libata.rst | 578 quiescent state. Timed out commands may succeed or fail any time.
|
| /linux-5.19.10/arch/ |
| D | Kconfig | 791 that need it, such as userspace RCU extended quiescent state.
|