Home
last modified time | relevance | path

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

123456789

/linux-6.12.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
Dswait.h115 * observe an empty wait list while the waiter might not observe @cond.
Dspinlock.h143 * it is forbidden that CPU0 does not observe CPU1's store to Y (r0 = 0)
144 * and CPU1 does not observe CPU0's store to X (r1 = 0); see the comments
162 * and CPU2 does not observe CPU0's store to X (r2 = 0); see the comments
/linux-6.12.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-6.12.1/fs/xfs/scrub/
Dagb_bitmap.c32 * the first btree record, we'll observe that bc_levels[0].ptr == 1, so we
33 * record that we saw block 1. Then we observe that bc_levels[1].ptr == 1, so
/linux-6.12.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-6.12.1/tools/testing/selftests/bpf/prog_tests/
Dmap_kptr.c151 /* Observe refcount dropping to 1 on bpf_map_free_deferred */ in serial_test_map_kptr()
156 /* Observe refcount dropping to 1 on synchronous delete elem */ in serial_test_map_kptr()
/linux-6.12.1/kernel/locking/
Dosq_lock.c65 * will now observe @lock and will complete its in osq_wait_next()
170 * in which case we should observe @node->locked becoming in osq_lock()
Dqspinlock_paravirt.h364 * observe its next->locked value and advance itself. in pv_kick_node()
443 * when we observe _Q_SLOW_VAL in __pv_queued_spin_unlock() in pv_wait_head_or_lock()
444 * we'll be sure to be able to observe our hash entry. in pv_wait_head_or_lock()
/linux-6.12.1/arch/mips/include/asm/
Dsync.h28 * other coherent CPUs will observe their completion before they observe
/linux-6.12.1/kernel/time/
Dsched_clock.c113 * sched_clock() will never observe mis-matched data even if called from
265 * at the end of the critical section to be sure we observe the
/linux-6.12.1/sound/firewire/bebob/
Dbebob_yamaha_terratec.c26 * to observe device's state, mainly check cmp connection and signal format. I
/linux-6.12.1/Documentation/i2c/
Di2c-stub.rst38 4. observe its behavior in the kernel log
/linux-6.12.1/fs/
Dinternal.h135 * caller is able to observe any changes done by the remount. This holds until
156 * observe all the changes remount did to the superblock.
/linux-6.12.1/net/netfilter/
Dnft_set_bitmap.c26 * If no transaction is going on, we observe all elements are in the following
34 * On transaction handling, we observe these two temporary states:
/linux-6.12.1/Documentation/dev-tools/
Dkcsan.rst187 Larger values result in the window in which we may observe a race to
248 manifest rarely), and (b) be able to actually observe them. We can accomplish
253 address set up, and then observe the watchpoint to fire, two accesses to the
/linux-6.12.1/kernel/
Djump_label.c171 * static_key_dec_not_one() observe the positive value, in static_key_slow_inc_cpuslocked()
172 * they must also observe all the text changes. in static_key_slow_inc_cpuslocked()
177 * While holding the mutex this should never observe in static_key_slow_inc_cpuslocked()
303 * It should be impossible to observe -1 with jump_label_mutex held, in __static_key_slow_dec_cpuslocked()
/linux-6.12.1/tools/testing/selftests/tty/
Dtty_tstamp_update.c74 /* We need to wait at least 8 seconds in order to observe timestamp change */ in main()
/linux-6.12.1/Documentation/staging/
Dspeculation.rst16 observe its impact on microarchitectural state, such as the presence or
/linux-6.12.1/Documentation/driver-api/mtd/
Dspi-intel.rst82 10) Now you can reboot your board and observe the new BIOS starting up
/linux-6.12.1/net/core/
Dgro_cells.c120 /* We need to observe an rcu grace period before freeing ->cells, in gro_cells_destroy()
/linux-6.12.1/drivers/firmware/tegra/
Divc.c472 * Notify remote end to observe state transition. in tegra_ivc_notified()
512 * Notify remote end to observe state transition. in tegra_ivc_notified()
536 * Notify remote end to observe state transition. in tegra_ivc_notified()
/linux-6.12.1/kernel/futex/
Dpi.c384 * observe this state, wait_lock is irrelevant. in __attach_to_pi_owner()
1011 * handoff -- such that the latter can observe the futex_q::pi_state in futex_lock_pi()
1018 * such that futex_unlock_pi() is guaranteed to observe the waiter when in futex_lock_pi()
1164 * wake_futex_pi() must observe any new waiters. in futex_unlock_pi()
1173 * complete such that we're guaranteed to observe the in futex_unlock_pi()

123456789