Home
last modified time | relevance | path

Searched refs:smp_store_release (Results 1 – 25 of 31) sorted by relevance

12

/tools/memory-model/litmus-tests/
DMP+pooncerelease+poacquireonce.litmus6 * This litmus test demonstrates that smp_store_release() and
16 smp_store_release(flag, 1);
DWRC+pooncerelease+fencermbonceonce+Once.litmus9 * specifically, this litmus test is forbidden because smp_store_release()
25 smp_store_release(y, 1);
DISA2+pooncerelease+poacquirerelease+poacquireonce.litmus19 smp_store_release(y, 1);
27 smp_store_release(z, 1);
DZ6.0+pooncerelease+poacquirerelease+fencembonceonce.litmus22 smp_store_release(y, 1);
30 smp_store_release(z, 1);
DLB+poacquireonce+pooncerelease.litmus18 smp_store_release(y, 1);
DS+poonceonces.litmus7 * first store against P1()'s final load, if the smp_store_release()
DMP+fencewmbonceonce+fencermbonceonce.litmus8 * is usually better to use smp_store_release() and smp_load_acquire().
DISA2+poonceonces.litmus8 * smp_store_release() invocations are replaced by WRITE_ONCE() and all
DMP+polocks.litmus7 * stand in for smp_load_acquire() and smp_store_release(), respectively.
DMP+porevlocks.litmus7 * stand in for smp_load_acquire() and smp_store_release(), respectively.
/tools/include/asm/
Dbarrier.h50 #ifndef smp_store_release
51 # define smp_store_release(p, v) \ macro
/tools/arch/ia64/include/asm/
Dbarrier.h46 #define smp_store_release(p, v) \ macro
/tools/arch/s390/include/asm/
Dbarrier.h31 #define smp_store_release(p, v) \ macro
/tools/arch/powerpc/include/asm/
Dbarrier.h33 #define smp_store_release(p, v) \ macro
/tools/arch/sparc/include/asm/
Dbarrier_64.h43 #define smp_store_release(p, v) \ macro
/tools/include/linux/
Dring_buffer.h71 smp_store_release(&base->data_tail, tail); in ring_buffer_write_tail()
/tools/arch/x86/include/asm/
Dbarrier.h33 #define smp_store_release(p, v) \ macro
/tools/arch/arm64/include/asm/
Dbarrier.h27 #define smp_store_release(p, v) \ macro
/tools/memory-model/Documentation/
Dordering.txt261 Release operations include smp_store_release(), atomic_set_release(),
266 For example, use of smp_store_release() saves a line compared to the
270 smp_store_release(&y, 1);
272 More important, smp_store_release() makes it easier to connect up the
274 by the smp_store_release(), in this case "y", will normally be used in
286 smp_store_release(), which still provides the needed ordering of "x"
287 against "y". On x86, the version using smp_store_release() might compile
295 smp_store_release(), but also atomic_set_release(), and
299 smp_store_release() except that: (1) It takes the pointer to
330 As with smp_store_release(), this also makes it easier to connect
[all …]
Drecipes.txt216 Use of smp_store_release() and smp_load_acquire() is one way to force
223 smp_store_release(&y, 1);
232 The smp_store_release() macro orders any prior accesses against the
246 use of smp_store_release() and smp_load_acquire(), except that both
273 smp_store_release(), but the rcu_dereference() macro orders the load only
290 It is usually better to use smp_store_release() instead of smp_wmb()
416 smp_store_release(&y, 1);
422 smp_store_release(&z, 1);
445 smp_store_release(&y, 1);
451 smp_store_release(&z, 1);
Dcontrol-dependencies.txt92 you must use explicit memory ordering, for example, smp_store_release():
96 smp_store_release(&b, 1);
99 smp_store_release(&b, 1);
223 smp_load_acquire(), smp_store_release(), or, in the case of prior
229 smp_store_release(). Please note that it is *not* sufficient to use
Dglossary.txt129 macro such as "r1 = READ_ONCE(x)" or "smp_store_release(&a, 1)".
138 smp_store_release() pairs with an smp_load_acquire() that reads
169 An example special release store is smp_store_release(), but
/tools/lib/bpf/
Dringbuf.c238 smp_store_release(r->consumer_pos, in ringbuf_process_ring()
245 smp_store_release(r->consumer_pos, cons_pos); in ringbuf_process_ring()
/tools/memory-model/
Dlinux-kernel.def13 smp_store_release(X,V) { __store{release}(*X,V); }
61 atomic_set_release(X,V) { smp_store_release(X,V); }
Dlinux-kernel.bell17 'release (*smp_store_release*) ||

12