Home
last modified time | relevance | path

Searched refs:it (Results 1 – 25 of 127) sorted by relevance

123456

/tools/testing/selftests/sync/
Dsync_stress_consumer.c108 int fence, merged, tmp, valid, it, i; in mpcs_consumer_thread() local
114 for (it = 1; it <= iterations; it++) { in mpcs_consumer_thread()
115 fence = sw_sync_fence_create(producer_timelines[0], "name", it); in mpcs_consumer_thread()
118 "name", it); in mpcs_consumer_thread()
140 ASSERT(test_data_mpsc.counter == n * it, in mpcs_consumer_thread()
/tools/lib/traceevent/Documentation/
Dlibtraceevent-func_find.txt21 address. The given address does not have to be exact, it will select the function
22 that would contain it.
28 by given address _addr_. The _addr_ does not have to be exact, it will select the
29 function that would contain it. The _tep_ argument is the trace event parser context.
34 it cannot be found.
37 or 0 in case it cannot be found.
Dlibtraceevent-func_apis.txt28 allow them to keep using it instead of duplicating all the entries inside.
33 function, which has to be resolved. In case of success, it should return
49 address. The given address does not have to be exact, it will select
50 the function that would contain it.
56 by given address _addr_. The _addr_ does not have to be exact, it will select
57 the function that would contain it. The _tep_ argument is the trace event
70 it was stored in the kernel. Some strings internal to the kernel with static
75 context. The _fmt_ is the string to register, it is copied internally.
85 it cannot be found.
88 or 0 in case it cannot be found.
Dlibtraceevent-handle.txt31 When there is no more references, then it will free the handler, as well
32 as clean up all its resources that it had used. The argument _tep_ is
39 it had used are cleaned up.
46 NULL is returned in case there is not enough free memory to allocate it.
Dlibtraceevent-cpus.txt7 buffer representing it. Note, the buffer may be empty.
22 buffer representing it. The _tep_ argument is trace event parser context.
25 buffer representing it. The _tep_ argument is trace event parser context.
/tools/usb/usbip/
DCOPYING7 of this license document, but changing it is not allowed.
12 freedom to share and change it. By contrast, the GNU General Public
17 using it. (Some other Free Software Foundation software is covered by
18 the GNU Library General Public License instead.) You can apply it to
24 this service if you wish), that you receive source code or can get it
25 if you want it, that you can change the software or use pieces of it
31 distribute copies of the software, or if you modify it.
53 program proprietary. To prevent this, we have made it clear that any
63 a notice placed by the copyright holder saying it may be distributed
67 that is to say, a work containing the Program or a portion of it,
[all …]
DINSTALL8 unlimited permission to copy, distribute and modify it.
22 definitions. Finally, it creates a shell script `config.status' that
38 may remove or edit it.
42 you want to change it or regenerate `configure' using a newer version
50 Running `configure' might take a while. While running, it prints
51 some messages telling which features it is checking for.
66 for the package's developers. If you use it, you may have to get
98 With a non-GNU `make', it is safer to compile the package for one
122 If the package supports it, you can cause programs to be installed
137 find the X include and library files automatically, but if it doesn't,
[all …]
/tools/bpf/bpftool/Documentation/
Dbpftool-struct_ops.rst37 If *STRUCT_OPS_MAP* is specified, it shows information only
38 for the given struct_ops. Otherwise, it lists all struct_ops
46 If *STRUCT_OPS_MAP* is specified, it dumps information only
47 for the given struct_ops. Otherwise, it dumps all struct_ops
Dbpftool-iter.rst38 and pin it to *PATH*. The *PATH* should be located
64 Create a file-based bpf iterator from bpf_iter_netlink.o and pin it
72 id 20, and pin it to /sys/fs/bpf/my_hashmap
/tools/memory-model/litmus-tests/
DWRC+pooncerelease+fencermbonceonce+Once.litmus7 * the first write is moved to a separate process. Because it features
8 * a release and a read memory barrier, it should be forbidden. More
/tools/testing/selftests/arm64/signal/
DREADME16 by receiving some kind of fatal signal from the Kernel, so it's safer
38 kind of tests it is extremely easy in fact to end-up injecting other
39 unrelated SEGV bugs in the testcases, it becomes extremely tricky to
47 and verify if it is indeed GOOD or BAD (depending on what we were
52 default it takes care to verify that the test-execution had at least
/tools/objtool/Documentation/
Dstack-validation.txt14 For each function, it recursively follows all possible code paths and
20 instructions). Similarly, it knows how to follow switch statements, for
74 what it looks like instead:
88 The benefit of objtool here is that because it ensures that *all*
101 band. So it doesn't affect runtime performance and it can be
124 outside of a function, it flags an error since that usually indicates
152 the same value it had on function entry.
156 and it's not a sibling call, objtool has no way to follow the jump
157 because it only analyzes a single file at a time.
190 FRAME_END macros. Otherwise, if it's not a callable function, remove
[all …]
/tools/testing/ktest/examples/
DREADME2 The configs still need to be customized for your environment, but it
3 is broken up by task which makes it easier to understand how to set up
12 it easy to compile test different archs. You can download the arch
/tools/memory-model/Documentation/
Dexplanation.txt49 rather, it explains in English what the code expresses symbolically.
78 for the loads, the model will predict whether it is possible for the
102 device, stores it in a buffer, and sets a flag to indicate the buffer
106 ready, and if it is, copies the data back to userspace. The buffer
135 reads flag into the private variable r1, and if it is set, reads the
173 If this were to occur it would mean the driver contains a bug, because
174 incorrect data would get sent to the user: 0 instead of 1. As it
197 it, as loads can obtain values only from earlier stores.
202 P1 must load 0 from buf before P0 stores 1 to it; otherwise r2
206 P0 stores 1 to buf before storing 1 to flag, since it executes
[all …]
Dsimple.txt27 it is generally a mistake to assume your code will only run in a single
41 Code locking can severely limit both performance and scalability, so it
55 tuned to deal better with high contention. And for one final thing, it is
67 it more efficient. Nor is RCU unique: Similar batching optimizations
75 being completely single-threaded, it is often possible to use library
93 in the code execution that will execute as though it is single threaded.
118 In addition, it is sometimes necessary to occasionally update some global
138 and effective ways of using it that avoid the need to pay attention to
143 readers, but it won't be so simple. For example, such writes will be
148 primitives. (LKMM does not yet know about sequence locking, so it is
[all …]
/tools/perf/Documentation/
Dperf-inject.txt15 perf-inject reads a perf-record event stream and repipes it to stdout. At any
52 Decode Instruction Tracing data, replacing it with synthesized events.
69 Don't complain, do it.
78 without updating it. Currently this option is supported only by
Dperf-sched.txt30 of the workload as it occurred when it was recorded - and can repeat
31 it a number of times, measuring its performance.)
45 By default it shows the individual schedule events, including the wait
79 Don't complain, do it.
167 Show task state when it switched out.
Dperf-timechart.txt20 but it's possible to record IO (disk, network) activity using -I argument.
55 Don't complain, do it.
66 duration or tasks with given name. If number is given it's interpreted
67 as number of nanoseconds. If non-numeric string is given it's
78 Reduces number of figures on the SVG and makes it more render-friendly.
Dperf-buildid-cache.txt16 files to/from the cache. In the future it should as well set upper limits for
19 record it along with the buildid-cache, which will be used by perf-probe.
29 Don't complain, do it.
79 it follows the same syntax as the DEBUGINFOD_URLS variable, like:
Dperf-kvm.txt27 of an arbitrary workload and save it into a perf data file. We set the
90 Guest os /proc/kallsyms file copy. 'perf' kvm' reads it to get guest
91 kernel symbols. Users copy it out from guest os.
93 Guest os /proc/modules file copy. 'perf' kvm' reads it to get guest
94 kernel module information. Users copy it out from guest os.
156 When processing pre-existing threads /proc/XXX/mmap, it may take
Dperf-report.txt110 --time-quantum (default 100ms). Specify with overhead and before it.
141 sampled IPC in this function. IPC means Instruction Per Cycle. If it's low,
142 it indicates there may be a performance bottleneck when the function is
144 and low IPC, it's worth further analyzing it to optimize its performance.
175 omitted, it searches all events for matching field name. The matched
179 be shortened to 'switch' as long as it's not ambiguous. Also event can
195 Also it can contain any sort key(s).
200 If the keys starts with a prefix '+', then it will append the specified
206 function and searched through the callchain, thus it requires callchain
223 with a '.' character, that thus it's the only non valid separator.
[all …]
/tools/power/cpupower/
DToDo13 monitor to outside it. This can be given higher
23 This would be ideal as it will not introduce noise in the
/tools/scripts/
Dutilities.mak111 # which can handle it just fine).
115 # not it contains a newline.
120 # processes the resulting escaped text, it transforms
121 # it into the original unescaped text.
163 # the `command -v' is defined by POSIX, but it's not
164 # necessarily very portable, so it's only used if
/tools/perf/scripts/perl/Perf-Trace-Util/
DREADME17 that you want to access - it's passed as the second parameter,
52 This library is free software; you can redistribute it and/or modify
53 it under the same terms as Perl itself, either Perl version 5.10.0 or,
/tools/testing/selftests/tc-testing/creating-plugins/
DAddingPlugins.txt47 and the post_suite method can refer to it when dumping the "skipped"
85 can use it.
91 arguments to it. Care should be taken that the new arguments do not
104 eg: raise Exception('plugin xxx, arg -y is wrong, fix it')

123456