Home
last modified time | relevance | path

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

12345678910>>...15

/kernel/linux/linux-6.6/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.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
Dswait.h115 * observe an empty wait list while the waiter might not observe @cond.
/kernel/linux/linux-5.10/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.h138 * it is forbidden that CPU0 does not observe CPU1's store to Y (r0 = 0)
139 * and CPU1 does not observe CPU0's store to X (r1 = 0); see the comments
157 * 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.
/kernel/linux/linux-5.10/kernel/kcsan/
Dkcsan.h102 * Did not observe a value-change, however, it is valid to report the
108 * Did not observe a value-change, and it is invalid to report the race.
/kernel/linux/linux-6.6/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.
/kernel/linux/linux-6.6/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
/kernel/linux/linux-5.10/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
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-firmware-sfi12 can observe them this way::
/kernel/linux/linux-6.6/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()
/kernel/linux/linux-5.10/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 becomming in osq_lock()
/kernel/linux/linux-6.6/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()
/kernel/linux/linux-5.10/arch/mips/include/asm/
Dsync.h28 * other coherent CPUs will observe their completion before they observe
/kernel/linux/linux-6.6/arch/mips/include/asm/
Dsync.h28 * other coherent CPUs will observe their completion before they observe
/kernel/linux/linux-5.10/kernel/time/
Dsched_clock.c102 * sched_clock() will never observe mis-matched data even if called from
256 * at the end of the critical section to be sure we observe the
/kernel/linux/linux-5.10/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
/kernel/linux/linux-6.6/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()
/kernel/linux/linux-6.6/fs/
Dinternal.h122 * caller is able to observe any changes done by the remount. This holds until
143 * observe all the changes remount did to the superblock.
/kernel/linux/linux-6.6/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
/kernel/linux/linux-5.10/sound/firewire/bebob/
Dbebob_yamaha_terratec.c26 * to observe device's state, mainly check cmp connection and signal format. I
/kernel/linux/linux-6.6/sound/firewire/bebob/
Dbebob_yamaha_terratec.c26 * to observe device's state, mainly check cmp connection and signal format. I

12345678910>>...15