Home
last modified time | relevance | path

Searched refs:equal (Results 1 – 19 of 19) sorted by relevance

/tools/memory-model/Documentation/
Dlocking.txt45 consequence that if the final value of r0 is equal to 1, then the final
46 value of r1 must also be equal to 1. In contrast, the weaker rule would
77 This also has the consequence that if the final value of r1 is equal
78 to 0, then the final value of r0 must also be equal to 0. In contrast,
260 equal "0" and "1:r1" to equal 1.
292 If "1:r0" is equal to "0", "1:r1" can never equal "1" because CPU0()
Drecipes.txt91 consequence that if the final value of r0 is equal to 1, then the final
92 value of r1 must also be equal to 1. In contrast, the weaker rule would
117 This also has the consequence that if the final value of r1 is equal
118 to 0, then the final value of r0 must also be equal to 0. In contrast,
379 barrier in CPU1() prevents r0 and r1 from both ending up equal to 1.
Dglossary.txt84 are all equal to zero is forbidden by LKMM.
Dcontrol-dependencies.txt133 (q % MAX) must be equal to zero, regardless of the value of "q".
Dlitmus-tests.txt176 loaded a value from "x" that was equal to 1 but loaded a value from "y"
177 that was still equal to zero.
876 all executions in which "2:r0" is not equal to the value "1".
Dexplanation.txt1190 second load executed. So why doesn't r2 end up equal to 1?
1302 been forwarded to the load, so r1 would have ended up equal to 1, not
1452 be equal to X). Because of the cumul-fence links, we know that W will
1656 1. G = W is po-before or equal to X;
2029 This waits until s is equal to 0 and then atomically sets it to 1,
2040 which atomically sets s to 1 if it is currently equal to 0 and returns
Dordering.txt189 value being overwritten is almost always equal to the new value. Such a
/tools/perf/ui/
Dhist.c519 .equal = hpp__equal, \
533 .equal = hpp__equal, \
546 .equal = hpp__equal, \
683 if (acc->equal(acc, fmt)) { in perf_hpp__cancel_cumulate()
688 if (ovh->equal(ovh, fmt)) in perf_hpp__cancel_cumulate()
695 return a->equal && a->equal(a, b); in fmt_equal()
/tools/perf/tests/
Dattr.py108 def equal(self, other): member in Event
311 if (exp_event.equal(res_event)):
/tools/testing/selftests/bpf/prog_tests/
Dcore_reloc.c1004 int err, i, equal, fd; in run_core_reloc_tests() local
1118 equal = memcmp(data->out, test_case->output, in run_core_reloc_tests()
1120 if (CHECK(!equal, "check_result", in run_core_reloc_tests()
/tools/build/
DBuild.include31 # Check if both arguments has same arguments. Result is empty string if equal.
/tools/scripts/
Dutilities.mak185 # To compare if a 3 component version is greater or equal to another, first use
/tools/perf/util/
Dhist.h469 bool (*equal)(struct perf_hpp_fmt *a, struct perf_hpp_fmt *b); member
Dsort.c2689 hse->hpp.equal = __sort__hpp_equal; in __sort_dimension__alloc_hpp()
3058 hde->hpp.equal = __sort__hde_equal; in __alloc_dynamic_entry()
/tools/perf/Documentation/
Djitdump-specification.txt103 …ate new code started address for the jitted code. By default it should be equal to the vma address.
Dperf-config.txt645 Do not suppress syscall arguments that are equal to zero.
Dperf-stat.txt510 Print the top-down statistics that equal the input level. It allows
/tools/perf/
Dbuiltin-kvm.c411 fmt->equal = fmt_equal; in get_format()
Dbuiltin-c2c.c1963 fmt->equal = fmt_equal; in get_format()