Home
last modified time | relevance | path

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

12

/openbmc/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 …]
/openbmc/qemu/qapi/
H A Dvfio.json24 # @running-p2p: The device is running in the P2P quiescent state.
29 # @pre-copy-p2p: The device is running in the P2P quiescent state,
/openbmc/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 …]
/openbmc/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 quiescent-state information from the leaves to the root and also that
[all …]
/openbmc/qemu/docs/devel/migration/
H A Dvfio.rst27 themselves, VFIO migration uAPI defines an intermediate P2P quiescent state.
28 While in the P2P quiescent state, P2P DMA transactions cannot be initiated by
34 quiescent state and only then are they stopped or started. This makes migration
173 The VFIO device is first put in P2P quiescent state
200 The VFIO device is first put in P2P quiescent state
/openbmc/linux/Documentation/devicetree/bindings/regulator/
H A Dsprd,sc2731-regulator.txt3 The SC2731 integrates low-voltage and low quiescent current DCDC/LDO.
/openbmc/linux/Documentation/networking/
H A Dipvs-sysctl.rst175 persistent templates when the destination server is quiescent.
177 quiescent by setting its weight to 0 and it is desired that
180 connections are allowed to quiescent destination servers.
184 connection and the destination server is quiescent.
/openbmc/linux/drivers/scsi/megaraid/
H A Dmegaraid_ioctl.h284 uint32_t quiescent; member
H A Dmega_common.h156 uint8_t quiescent; member
H A Dmegaraid_mm.c162 if (!adp->quiescent) { in mraid_mm_ioctl()
715 adp->quiescent = 0; in lld_ioctl()
929 adapter->quiescent = 1; in mraid_mm_register_adp()
H A Dmegaraid_mbox.c1875 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()
/openbmc/linux/kernel/time/
H A DKconfig156 tracking to enter/exit RCU extended quiescent states.
173 userspace extended quiescent state and tickless cputime
/openbmc/linux/Documentation/admin-guide/cgroup-v1/
H A Dfreezer-subsystem.rst16 quiescent state. Once the tasks are quiescent another task can
/openbmc/linux/drivers/scsi/
H A Dmegaraid.c406 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()
2094 atomic_read(&adapter->quiescent)); in proc_show_config()
3778 atomic_set(&adapter->quiescent, 1); in mega_del_logdrv()
3805 atomic_set(&adapter->quiescent, 0); in mega_del_logdrv()
4083 if (atomic_read(&adapter->quiescent) == 0) in mega_internal_command()
4391 atomic_set(&adapter->quiescent, 0); in megaraid_probe_one()
H A Dmegaraid.h854 atomic_t quiescent; /* a stage reached when delete logical member
/openbmc/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 …]
/openbmc/linux/Documentation/RCU/
H A Dstallwarn.rst273 The "fqs=" shows the number of force-quiescent-state idle/offline
297 If all CPUs and tasks have passed through quiescent states, but the
306 of jiffies between force-quiescent-state scans, in this case three,
319 through the required quiescent states. The "g" number shows the current
H A Drcubarrier.rst363 since each CPU must undergo a context switch (or other quiescent
/openbmc/linux/kernel/rcu/
H A DKconfig85 idle, and user-mode execution as quiescent states. Not for
101 user-mode execution as quiescent states. It forces IPIs and
/openbmc/qemu/docs/devel/
H A Drcu.rst168 will have to report quiescent points regularly, either manually
173 It is not a problem if such a thread reports quiescent points,
H A Dtcg-plugins.rst163 has executed while all vCPUs are quiescent.
/openbmc/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.
/openbmc/linux/Documentation/admin-guide/
H A 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.
H A Dtainted-kernels.rst139 the update happens when the system is as quiescent as possible. However,
/openbmc/linux/Documentation/virt/kvm/devices/
H A Darm-vgic-its.rst205 - The ITS is not enabled and quiescent

12