Searched refs:never (Results 1 – 13 of 13) sorted by relevance
| /tools/testing/selftests/bpf/progs/ |
| A D | core_kern.c | 64 volatile const int never; variable
90 if (never) { \ in balancer_ingress()
|
| /tools/testing/selftests/net/netfilter/packetdrill/ |
| A D | conntrack_synack_old.pkt | 7 // This reset never makes it to the endpoint, elided in the packetdrill script
|
| /tools/memory-model/Documentation/ |
| A D | locking.txt | 186 never acquired the lock, and thus did not fully benefit from the lock's
297 If "1:r0" is equal to "0", "1:r1" can never equal "1" because CPU0()
|
| A D | explanation.txt | 213 However, real computer hardware almost never follows the Sequential
340 on different CPUs are never linked by po. Also, it is by definition
363 (unless it can prove the accesses will never be executed), it will not
729 On the other hand, stores to different memory locations are never
730 related by co, just as instructions on different CPUs are never
983 value of x will be the initial value plus two. We should never have
1222 then we would never get r1 = &x and r2 = 0. By the time P1 executed
1526 Grace-Period Guarantee, which states that a critical section can never
1565 never end with r1 = 1 and r2 = 0. The reasoning is as follows. r1 = 1
1954 Fortunately this won't matter, assuming that litmus tests never do
|
| A D | litmus-tests.txt | 128 by reference, hence "P0(int *x, int *y)", but *never* "P0(int x, int y)".
202 indicates that the bad result flagged by the "exists" clause never
978 can never be 0 in the if condition. As a result, said clever
|
| A D | recipes.txt | 160 CPU2() never acquired the lock, and thus did not benefit from the
|
| A D | ordering.txt | 524 so that there are never concurrent conflicting accesses to
|
| /tools/power/cpupower/bench/ |
| A D | README-BENCH | 84 will always see 50% loads and you get worst performance impact never
|
| /tools/perf/Documentation/ |
| A D | perf-annotate.txt | 85 'always', 'never' or 'auto', allowing configuring color output
|
| A D | perf-report.txt | 339 'always', 'never' or 'auto', allowing configuring color output
|
| A D | perf-record.txt | 703 overwrite the oldest records, that thus will never make it to the
|
| A D | perf-intel-pt.txt | 493 never need to specify this term.
|
| /tools/testing/selftests/wireguard/ |
| A D | netns.sh | 29 export WG_HIDE_KEYS=never
|
Completed in 23 milliseconds