Searched refs:calls (Results 1 – 25 of 53) sorted by relevance
123
| /tools/testing/selftests/bpf/progs/ |
| D | test_cgroup_link.c | 6 int calls = 0; variable
12 __sync_fetch_and_add(&calls, 1); in egress()
|
| /tools/perf/scripts/python/bin/ |
| D | export-to-sqlite-report | 19 calls=$3
29 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/export-to-sqlite.py $dbname $columns $calls
|
| D | export-to-postgresql-report | 19 calls=$3
29 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/export-to-postgresql.py $dbname $columns $calls
|
| /tools/perf/Documentation/ |
| D | perf-bench.txt | 212 Suite for evaluating wake calls.
215 Suite for evaluating parallel wake calls.
218 Suite for evaluating requeue calls.
221 Suite for evaluating futex lock_pi calls.
226 Suite for evaluating concurrent epoll_wait calls.
229 Suite for evaluating multiple epoll_ctl calls.
|
| D | Build.txt | 14 top level Makefile working as a wrapper that calls the main
|
| D | intel-bts.txt | 13 code is still needed to pair up calls and returns correctly, consequently much
|
| D | itrace.txt | 3 c synthesize branches events (calls only)
|
| /tools/io_uring/ |
| D | io_uring-bench.c | 83 unsigned long calls; member
318 s->calls++; in submitter_fn()
483 unsigned long done, calls, reap; in main() local
563 reap = calls = done = 0; in main()
572 this_call += s->calls; in main()
574 if (this_call - calls) { in main()
575 rpc = (this_done - done) / (this_call - calls); in main()
576 ipc = (this_reap - reap) / (this_call - calls); in main()
584 calls = this_call; in main()
|
| D | README | 25 comes with man pages for the three system calls.
|
| /tools/power/pm-graph/config/ |
| D | cgskip.txt | 7 # as leaves with no child calls. It can be editted by
27 # console calls
|
| D | custom-timeline-functions.cfg | 28 # Display function calls
72 # Function calls to display in the timeline alongside device callbacks.
77 # The function calls are displayed on the timeline alongside the device blocks.
139 # Dev mode function calls to display inside timeline entries
142 # The function calls are displayed on the timeline alongside the device blocks.
|
| D | freeze-dev.cfg | 2 # Dev S2 (Freeze) test - includes src calls / kernel threads
49 # Display function calls
|
| D | suspend-dev.cfg | 2 # Dev S3 (Suspend to Mem) test - includes src calls / kernel threads
49 # Display function calls
|
| D | standby-dev.cfg | 2 # Dev S1 (Standby) test - includes src calls / kernel threads
49 # Display function calls
|
| D | standby.cfg | 49 # Display function calls
|
| D | freeze.cfg | 49 # Display function calls
|
| D | standby-callgraph.cfg | 50 # Display function calls
|
| D | suspend.cfg | 49 # Display function calls
|
| D | suspend-callgraph.cfg | 50 # Display function calls
|
| D | suspend-x2-proc.cfg | 49 # Display function calls
|
| /tools/testing/selftests/bpf/prog_tests/ |
| D | cgroup_link.c | 15 skel->bss->calls = 0; in ping_and_check()
18 if (CHECK(skel->bss->calls != exp_calls, "call_cnt", in ping_and_check()
19 "exp %d, got %d\n", exp_calls, skel->bss->calls)) in ping_and_check()
|
| /tools/power/pm-graph/ |
| D | README | 154 Developer mode adds information on low level source calls to the timeline.
155 The tool sets kprobes on all delay and mutex calls to see which devices
157 subsystem dependent calls to better fill out the timeline.
240 Add kernel source calls and threads to the timeline (default: disabled).
433 the tool adds the sys_sync and freeze_processes calls as virtual device blocks
434 in the timeline to show you where the time is going. These calls should fill
437 It is possible to add new function calls to the timeline by adding them to
444 custom calls, or leave it false to append them to the internal ones.
486 Here is a full example entry. It displays cpu resume calls in the timeline
499 The function calls are displayed inside the main device/call blocks in the
[all …]
|
| /tools/objtool/Documentation/ |
| D | stack-validation.txt | 137 3. Each callable function which calls another function must have the
173 For C files, the common culprits are inline asm statements and calls to
288 3) If funcA() calls an inline function, the object code for funcA()
302 The intention of the warning is to prevent calls to funcB() from eventually
306 It also helps verify that there are no unexpected calls to funcB() which may
310 1) remove explicit calls to funcB() from funcA().
311 2) add the correct guards before and after calls to low level functions like
315 function tracing inserts additional calls, which is not obvious from the
|
| /tools/testing/selftests/media_tests/ |
| D | regression_test.txt | 28 sleep 10 in between the ioctl calls.
|
| /tools/perf/scripts/perl/Perf-Trace-Util/ |
| D | README | 7 that the core perf support for Perl calls on and should always be
|
123