Searched refs:started (Results 1 – 18 of 18) sorted by relevance
| /tools/virtio/ |
| D | virtio_test.c | 173 long started = 0, completed = 0, next_reset = reset_n; in run_test() local
189 started_before = started; in run_test()
195 while (started < bufs && in run_test()
196 (started - completed) < batch) { in run_test()
199 dev->buf + started, in run_test()
203 started > started_before) in run_test()
210 ++started; in run_test()
218 if (started >= bufs) in run_test()
251 started = completed; in run_test()
256 if (completed == completed_before && started == started_before) in run_test()
[all …]
|
| /tools/virtio/ringtest/ |
| D | main.c | 110 int started = 0; in run_guest() local
123 if (started < bufs && in run_guest()
124 started - completed < max_outstanding) { in run_guest()
127 ++started; in run_guest()
149 assert(started <= bufs); in run_guest()
|
| /tools/testing/kunit/ |
| D | kunit_parser.py | 222 started = False
226 if not started and KTAP_START.search(line):
231 started = True
233 elif not started and TAP_START.search(line):
237 started = True
239 elif started and KTAP_END.search(line):
242 elif started:
|
| /tools/memory-model/Documentation/ |
| D | README | 21 that you need, and just want to get started with LKMM litmus
|
| D | ordering.txt | 384 prove that it started before a given call to rcu_read_lock(), then
|
| D | explanation.txt | 1567 synchronize_rcu(), so P0's critical section must have started before
2607 P1 before the critical section started and so would have been visible
|
| /tools/testing/selftests/seccomp/ |
| D | seccomp_bpf.c | 2514 sem_t *started; member
2543 sem_t started; in FIXTURE() local
2578 sem_init(&self->started, 0, 0); in FIXTURE_SETUP()
2581 self->sibling[0].started = &self->started; in FIXTURE_SETUP()
2589 self->sibling[1].started = &self->started; in FIXTURE_SETUP()
2619 sem_destroy(&self->started); in FIXTURE_TEARDOWN()
2635 sem_post(me->started); in tsync_sibling()
2693 sem_wait(&self->started); in TEST_F()
2731 sem_wait(&self->started); in TEST_F()
2761 sem_wait(&self->started); in TEST_F()
[all …]
|
| /tools/perf/util/ |
| D | auxtrace.c | 2332 bool started; member
2361 if (args->started) { in find_kern_sym_cb()
2372 args->started = true; in find_kern_sym_cb()
2439 if (!args.started) { in find_kern_sym()
2459 if (!args->started) { in find_entire_kern_cb()
2460 args->started = true; in find_entire_kern_cb()
2473 struct sym_args args = { .started = false }; in addr_filter__entire_kernel()
2477 if (err < 0 || !args.started) { in addr_filter__entire_kernel()
|
| /tools/testing/selftests/rcutorture/bin/ |
| D | kvm-remote.sh | 265 echo All batches started. `date` | tee -a "$oldrun/remote-log"
|
| /tools/perf/Documentation/ |
| D | perf-daemon.txt | 41 Each session is started with control setup (with perf record --control
|
| D | perf-arm-spe.txt | 145 +++*+++ Latency is the total latency from the point at which sampling started on that instruction, …
|
| D | jitdump-specification.txt | 103 …* uint64_t new_code_addr: alternate new code started address for the jitted code. By default it sh…
|
| D | perf-stat.txt | 229 'disable': disable events). Measurements can be started with events disabled using
|
| D | perf-script-python.txt | 417 You can quickly get started writing a script for a particular set of
|
| D | perf-record.txt | 735 Measurements can be started with events disabled using --delay=-1 option. Optionally
|
| D | perf-intel-pt.txt | 1273 Domain kubuntu20.04 started
1337 Domain kubuntu20.04 started
|
| /tools/testing/selftests/tc-testing/creating-testcases/ |
| D | AddingTestCases.txt | 68 this test was started: qdiscs deleted, actions flushed, etc.
|
| /tools/usb/usbip/ |
| D | COPYING | 104 when run, you must cause it, when started running for such
|