/tools/memory-model/ |
D | linux-kernel.def | 13 smp_store_release(X,V) { __store{release}(*X,V); } 15 rcu_assign_pointer(X,V) { __store{release}(X,V); } 32 xchg_release(X,V) __xchg{release}(X,V) 37 cmpxchg_release(X,V,W) __cmpxchg{release}(X,V,W) 71 atomic_add_return_release(V,X) __atomic_op_return{release}(X,+,V) 75 atomic_fetch_add_release(V,X) __atomic_fetch_op{release}(X,+,V) 80 atomic_inc_return_release(X) __atomic_op_return{release}(X,+,1) 84 atomic_fetch_inc_release(X) __atomic_fetch_op{release}(X,+,1) 89 atomic_sub_return_release(V,X) __atomic_op_return{release}(X,-,V) 93 atomic_fetch_sub_release(V,X) __atomic_fetch_op{release}(X,-,V) [all …]
|
D | linux-kernel.bell | 17 'release (*smp_store_release*) || 21 instructions W[{'once,'release}] 22 instructions RMW[{'once,'acquire,'release}]
|
D | README | 34 in this release. A compatible model will likely be made available in 35 a later release of Linux kernel. 37 If you absolutely need to run the model in this particular release, 41 dependency on a target kernel release where converted code is built 170 lock acquisition/release, and RCU operations. 199 Provides a front-end analysis of lock acquisition and release,
|
/tools/testing/selftests/bpf/progs/ |
D | test_btf_skc_cls_ingress.c | 107 goto release; in handle_ip6_tcp() 112 goto release; in handle_ip6_tcp() 125 goto release; in handle_ip6_tcp() 130 goto release; in handle_ip6_tcp() 143 release: in handle_ip6_tcp()
|
D | test_tcp_check_syncookie_kern.c | 88 goto release; in check_syncookie() 120 goto release; in check_syncookie() 147 release: in check_syncookie()
|
D | bpf_dctcp_release.c | 24 .release = (void *)dctcp_nouse_release,
|
/tools/memory-model/litmus-tests/ |
D | ISA2+pooncerelease+poacquirerelease+poacquireonce.litmus | 6 * This litmus test demonstrates that a release-acquire chain suffices 8 * that the release-acquire chain suffices is because in all but one 11 * (AKA non-rf) link, so release-acquire is all that is needed.
|
D | S+fencewmbonceonce+poacquireonce.litmus | 6 * Can a smp_wmb(), instead of a release, and an acquire order a prior
|
D | LB+poacquireonce+pooncerelease.litmus | 6 * Does a release-acquire pair suffice for the load-buffering litmus
|
D | S+poonceonces.litmus | 6 * Starting with a two-process release-acquire chain ordering P0()'s
|
D | ISA2+poonceonces.litmus | 6 * Given a release-acquire chain ordering the first process's store
|
D | README | 45 As below, but with store-release replaced with WRITE_ONCE() 49 Can a release-acquire chain order a prior store against 58 Does a release-acquire pair suffice for the load-buffering 63 As above, but with store-release replaced with WRITE_ONCE() 87 As below, but with a release-acquire chain. 129 Can a smp_wmb(), instead of a release, and an acquire order 149 Is the ordering provided by a release-acquire chain sufficient 151 not participate in that release-acquire chain?
|
D | WRC+pooncerelease+fencermbonceonce+Once.litmus | 8 * a release and a read memory barrier, it should be forbidden. More
|
D | Z6.0+pooncerelease+poacquirerelease+fencembonceonce.litmus | 6 * This litmus test shows that a release-acquire chain, while sufficient
|
/tools/lib/lockdep/ |
D | lockdep.c | 26 .release = "liblockdep", in init_utsname()
|
/tools/perf/util/ |
D | util.c | 362 strncpy(str, utsname.release, str_size); in fetch_kernel_version() 369 err = sscanf(utsname.release, "%d.%d.%d", in fetch_kernel_version() 374 utsname.release); in fetch_kernel_version()
|
D | llvm-utils.c | 254 char release[128]; in detect_kbuild_dir() local 261 err = fetch_kernel_version(NULL, release, in detect_kbuild_dir() 262 sizeof(release)); in detect_kbuild_dir() 266 test_dir = release; in detect_kbuild_dir()
|
/tools/power/cpupower/bench/ |
D | parse.c | 77 len += strlen(sysdata.nodename) + strlen(sysdata.release); in prepare_output() 88 dirname, sysdata.nodename, sysdata.release, time(NULL)); in prepare_output()
|
/tools/testing/selftests/wireguard/qemu/ |
D | init.c | 53 …eGuard Test Suite on ") + strlen(utsname.sysname) + strlen(utsname.release) + strlen(utsname… in print_banner() 54 …1b[45m\x1b[33m\x1b[1m%*.s\x1b[0m\n\n", len, "", utsname.sysname, utsname.release, utsname.machine,… in print_banner()
|
/tools/memory-model/Documentation/ |
D | glossary.txt | 35 When an acquire load returns the value stored by a release store 37 from" the release store), then all operations preceding that 169 An example special release store is smp_store_release(), but 171 release stores.
|
D | recipes.txt | 195 load buffering, release-acquire chains, store buffering. 237 The init_stack_slab() function in lib/stackdepot.c uses release-acquire 464 is that in this version, CPU2() is not part of the release-acquire chain. 467 Despite this limitation, release-acquire chains are low-overhead as 559 release-acquire chain suffices. Both the MP and the ISA2 566 locking and in the release-acquire sections.
|
/tools/testing/selftests/bpf/prog_tests/ |
D | core_extern.c | 16 if (sscanf(info.release, "%u.%u.%u", &major, &minor, &patch) != 3) in get_kernel_version()
|
/tools/testing/selftests/bpf/ |
D | bpf_tcp_helpers.h | 161 void (*release)(struct sock *sk); member
|
/tools/testing/selftests/rcutorture/doc/ |
D | rcu-test-image.txt | 39 # Replace "precise" below with your favorite Ubuntu release.
|
/tools/lib/bpf/ |
D | libbpf_probes.c | 60 if (sscanf(utsn.release, "%d.%d.%d", in get_kernel_version()
|