Searched refs:say (Results 1 – 8 of 8) sorted by relevance
| /tools/testing/selftests/kselftest/ |
| D | module.sh | 59 say "ok"
65 say() { function
71 say "$1 [FAIL]" >&2
76 say "$1 [SKIP]" >&2
|
| /tools/memory-model/Documentation/ |
| D | explanation.txt | 334 instructions are presented to a CPU's execution unit. Thus, we say
429 We say that two events are linked by a dependency relation when the
739 special case, we say that the store propagates to its own CPU at the
749 and we say that the store's value is forwarded to R. Otherwise, the
750 CPU asks the memory subsystem for the value to load and we say that R
768 premature executions; we simply say that the load executes at the
900 same store unspecified; let's say they are inserted in program order,
925 What does it mean to say that a read-modify-write (rmw) update, such
1608 CPUs. (Perhaps this fact should lead us to say that rcu-fence isn't
1929 Early versions of the LKMM had nothing to say about plain accesses.
[all …]
|
| D | recipes.txt | 93 say nothing about the final value of r1.
119 the weaker rule would say nothing about the final value of r0.
|
| D | litmus-tests.txt | 203 happens. This line might instead say "Sometimes" to indicate that the
204 bad result happened in some but not all executions, or it might say
|
| /tools/perf/Documentation/ |
| D | perf-stat.txt | 200 If wanting to monitor, say, 'cycles' for a cgroup and also for system wide, this
|
| D | perf-script-python.txt | 102 The options basically say to collect data for every syscall event
|
| D | perf-record.txt | 359 If wanting to monitor, say, 'cycles' for a cgroup and also for system wide, this
|
| /tools/usb/usbip/ |
| D | COPYING | 67 that is to say, a work containing the Program or a portion of it,
|