Home
last modified time | relevance | path

Searched full:observe (Results 1 – 25 of 179) sorted by relevance

12345678

/Linux-v6.1/include/linux/
Drbtree_latch.h22 * copy, this does not guarantee an iteration will not observe modifications.
135 * observe one complete tree. See the comment for raw_write_seqcount_latch().
138 * tree structure is stored before we can observe the new @node.
161 * always observe one complete tree. See the comment for
164 * It is assumed that @node will observe one RCU quiescent state before being
Derrno.h10 * codes, signal_pending() MUST be set. Note that ptrace can observe these
Dspinlock.h142 * it is forbidden that CPU0 does not observe CPU1's store to Y (r0 = 0)
143 * and CPU1 does not observe CPU0's store to X (r1 = 0); see the comments
161 * and CPU2 does not observe CPU0's store to X (r2 = 0); see the comments
Dswait.h115 * observe an empty wait list while the waiter might not observe @cond.
/Linux-v6.1/kernel/kcsan/
Dkcsan.h103 * Did not observe a value-change, however, it is valid to report the
109 * Did not observe a value-change, and it is invalid to report the race.
Dpermissive.h70 * The rules here will ignore the data races if we observe no more than in kcsan_ignore_data_race()
/Linux-v6.1/tools/perf/Documentation/
Dexamples.txt44 You can observe the statistical properties as well, by using the
157 Or you can observe the whole system's page allocations for 10
173 Or observe how fluctuating the page allocations are, via statistical
/Linux-v6.1/kernel/locking/
Dosq_lock.c62 * will now observe @lock and will complete its in osq_wait_next()
167 * in which case we should observe @node->locked becoming in osq_lock()
Dqspinlock_paravirt.h367 * observe its next->locked value and advance itself. in pv_kick_node()
447 * when we observe _Q_SLOW_VAL in __pv_queued_spin_unlock() in pv_wait_head_or_lock()
448 * we'll be sure to be able to observe our hash entry. in pv_wait_head_or_lock()
/Linux-v6.1/arch/mips/include/asm/
Dsync.h28 * other coherent CPUs will observe their completion before they observe
/Linux-v6.1/kernel/time/
Dsched_clock.c103 * sched_clock() will never observe mis-matched data even if called from
255 * at the end of the critical section to be sure we observe the
/Linux-v6.1/kernel/futex/
Dpi.c383 * observe this state, wait_lock is irrelevant. in __attach_to_pi_owner()
1017 * handoff -- such that the latter can observe the futex_q::pi_state in futex_lock_pi()
1024 * such that futex_unlock_pi() is guaranteed to observe the waiter when in futex_lock_pi()
1050 * observe this inconsistency. in futex_lock_pi()
1151 * wake_futex_p() must observe a state consistent with what we in futex_unlock_pi()
1155 * complete such that we're guaranteed to observe the in futex_unlock_pi()
/Linux-v6.1/sound/firewire/bebob/
Dbebob_yamaha_terratec.c26 * to observe device's state, mainly check cmp connection and signal format. I
/Linux-v6.1/Documentation/i2c/
Di2c-stub.rst38 4. observe its behavior in the kernel log
/Linux-v6.1/fs/xfs/scrub/
Dbitmap.c225 * the first btree record, we'll observe that bc_levels[0].ptr == 1, so we
226 * record that we saw block 1. Then we observe that bc_levels[1].ptr == 1, so
/Linux-v6.1/net/netfilter/
Dnft_set_bitmap.c25 * If no transaction is going on, we observe all elements are in the following
33 * On transaction handling, we observe these two temporary states:
/Linux-v6.1/Documentation/dev-tools/
Dkcsan.rst177 Larger values result in the window in which we may observe a race to
238 manifest rarely), and (b) be able to actually observe them. We can accomplish
243 address set up, and then observe the watchpoint to fire, two accesses to the
/Linux-v6.1/Documentation/staging/
Dspeculation.rst16 observe its impact on microarchitectural state, such as the presence or
/Linux-v6.1/Documentation/driver-api/mtd/
Dspi-intel.rst82 10) Now you can reboot your board and observe the new BIOS starting up
/Linux-v6.1/net/core/
Dgro_cells.c119 /* We need to observe an rcu grace period before freeing ->cells, in gro_cells_destroy()
/Linux-v6.1/drivers/firmware/tegra/
Divc.c459 * Notify remote end to observe state transition. in tegra_ivc_notified()
499 * Notify remote end to observe state transition. in tegra_ivc_notified()
523 * Notify remote end to observe state transition. in tegra_ivc_notified()
/Linux-v6.1/kernel/sched/
Dswait.c19 * task is already running, so it will observe condition true (or has already).
Dloadavg.c213 * See calc_global_nohz(), if we observe the new index, we also in calc_load_write_idx()
214 * need to observe the new update time. in calc_load_write_idx()
/Linux-v6.1/kernel/
Dutsname_sysctl.c31 * to observe. Should this be in kernel/sys.c ????
/Linux-v6.1/net/xdp/
Dxsk_queue.h68 * could observe the producer pointer being set and thus load the data
85 * barrier, the producer could observe the consumer pointer being set

12345678