Searched refs:do (Results 1 – 25 of 77) sorted by relevance
1234
| /tools/net/ynl/ |
| D | cli.py | 47 if args.do:
48 reply = ynl.do(args.do, attrs, args.flags)
|
| /tools/testing/selftests/ftrace/test.d/ |
| D | functions | 20 while read line; do
26 while read line; do
42 while read line; do
52 grep -v '^#' set_ftrace_filter | while read t; do
81 while read line; do
90 while [ $again -eq 1 ]; do
98 while read line; do
144 for i in "$@" ; do
|
| /tools/bootconfig/samples/ |
| D | bad-dotword.bconf | 1 # do not start keyword with .
|
| /tools/power/cpupower/po/ |
| D | pt.po | 235 " frequência mínina do CPU - frequência máxima do CPU - "
244 #. on Intel and AMD, but we assume boost capable machines can do that
294 msgstr " nenhum ou driver do cpufreq deconhecido está ativo nesse CPU\n"
319 msgstr " limites do hardware: "
329 msgstr " reguladores do cpufreq disponíveis: "
353 msgstr " frequência atual do CPU é "
363 msgstr " status do cpufreq: "
389 " com o núcleo do cpufreq *\n"
408 " -l, --hwlimits Determina a frequência mínima e máxima do CPU "
415 " -d, --driver Determina o driver do kernel do cpufreq usado *\n"
[all …]
|
| /tools/testing/selftests/rcutorture/doc/ |
| D | TREE_RCU-kconfig.txt | 31 nohz_full - do at least one.
32 maxcpu -- do at least one.
|
| /tools/memory-model/Documentation/ |
| D | simple.txt | 100 concurrently. This works because the buckets do not overlap with each
141 The basic keep-things-simple rule for sequence locking is "do not write
142 in read-side code". Yes, you can do writes from within sequence-locking
158 keep-things-simple rules for RCU are "do not write in read-side code"
159 and "do not update anything that is visible to and accessed by readers",
183 More recent kernels have operations that return a value but do not
212 hence they do not provide any ordering guarantees at all.
224 no ordering, but they do prevent the compiler from carrying out a number
248 translation process, and have long been ready, willing, and able to do so.
268 If the alternatives above do not do what you need, please look at the
|
| D | control-dependencies.txt | 5 do not support them. One purpose of this document is therefore to
118 But please note that you need to be careful what you do with the local
183 else-clause of the "if" statement in question. In particular, they do
220 However, they do *not* guarantee any other sort of ordering:
249 do *not* apply to code beyond the end of that "if" statement.
253 (*) Control dependencies do *not* provide multicopy atomicity. If you
257 (*) Compilers do not understand control dependencies. It is therefore
258 your job to ensure that they do not break your code.
|
| D | ordering.txt | 62 o Value-returning RMW atomic operations whose names do not end in
84 with non-void return types) whose names do not end in _acquire, _release,
101 with void return types) do not guarantee any ordering whatsoever. Nor do
106 operations such as atomic_read() do not guarantee full ordering, and
150 atomic_inc() implementations do not guarantee full ordering, thus
476 RMW atomic operations whose names do not end in _acquire or
479 and atomic64_fetch_xor_relaxed(). These operations do carry
501 and further do not guarantee "atomic" access. For example, the compiler
544 If you need to live more dangerously, please do take the time to
|
| /tools/memory-model/litmus-tests/ |
| D | MP+unlocklockonceonce+fencermbonceonce.litmus | 7 * first must propagate to each CPU before stores in the second do, even if
|
| D | LB+fencembonceonce+ctrlonceonce.litmus | 10 * to do the trick. (But the full memory barrier could be replaced with
|
| /tools/perf/Documentation/ |
| D | perf-evlist.txt | 25 Don't complain, do it.
|
| D | perf-buildid-list.txt | 32 Don't do ownership validation.
|
| D | perf-data.txt | 41 Don't complain, do it.
|
| D | callchain-overhead-calculation.txt | 25 /* do something */
29 /* do something */
|
| D | perf-config.txt | 133 If you want to add or modify several config items, you can do like
137 To modify the sort order of report functionality in user config file(i.e. `~/.perfconfig`), do
142 in system config file (i.e. `$(sysconf)/perfconfig`), do
146 To query the record mode of call graph, do
150 If you want to know multiple config key/value pairs, you can do like
154 To query the config value of sort order of call graph in user config file (i.e. `~/.perfconfig`), do
158 …uery the config value of buildid directory in system config file (i.e. `$(sysconf)/perfconfig`), do
228 'perf.data' file header to, at analysis time find what is needed to do
313 where do the instruction jump into as below.
442 The size of stack to dump in order to do post-unwinding. Default is 8192 (byte).
|
| D | perf-script-python.txt | 74 every time a system call occurs in the system. Our script will do
76 that script. Theoretically, there are a couple of ways we could do
208 rid of everything to do with printing as well as the trace_begin() and
231 generate some results to print. To do that we need to have our
232 sys_enter() handler do the necessary tallying until all events have
255 exception. Well, there may be a better way to do this in Python but
393 Once you've done that (don't forget to do a new 'make install',
426 do basic things like aggregate event data, print results, etc. Also,
528 gives scripts a chance to do setup tasks:
536 processed and gives scripts a chance to do end-of-script tasks, such
|
| D | perf-script-perl.txt | 32 do basic things like aggregate event data, print results, etc. Also,
133 gives scripts a chance to do setup tasks:
142 processed and gives scripts a chance to do end-of-script tasks, such
|
| /tools/testing/selftests/tc-testing/creating-plugins/ |
| D | AddingPlugins.txt | 48 TAP output. The tdc.py script will do that for the test suite as
91 arguments to it. Care should be taken that the new arguments do not
100 The check_args method is so that the plugin can do validation on
|
| /tools/perf/scripts/perl/Perf-Trace-Util/ |
| D | README | 11 executable; scripts wishing to do that should 'use Context.pm'.
20 After you do that:
|
| /tools/bpf/bpftool/bash-completion/ |
| D | bpftool | 13 for w in $*; do
15 for (( idx=3; idx < ${#words[@]}-1; idx++ )); do
31 for w in $*; do
32 for (( idx=3; idx < ${#words[@]}-1; idx++ )); do
140 for (( idx=3; idx < ${#words[@]}-1; idx++ )); do
171 for (( idx=7; idx < ${#words[@]}-1; idx++ )); do
217 for (( idx=7; idx < ${#words[@]}-1; idx++ )); do
297 for (( i=1; i < ${#words[@]}; )); do
825 for (( idx=3; idx < ${#words[@]}-1; idx++ )); do
833 for (( idx=3; idx < ${#words[@]}-1; idx++ )); do
|
| /tools/testing/selftests/tc-testing/ |
| D | TODO.txt | 21 trying to run a function that will do nothing.
|
| /tools/lib/perf/Documentation/ |
| D | libperf-counting.txt | 40 The first thing you need to do before using libperf is to call init function:
158 From this moment events are counting and we can do our workload.
|
| /tools/usb/usbip/ |
| D | COPYING | 26 in new free programs; and that you know you can do these things.
117 themselves, then this License, and its terms, do not apply to those
136 Sections 1 and 2 above provided that you also do one of the following:
183 prohibited by law if you do not accept this License. Therefore, by
185 Program), you indicate your acceptance of this License to do so, and
200 otherwise) that contradict the conditions of this License, they do not
288 To do so, attach the following notices to the program. It is safest
339 library. If this is what you want to do, use the GNU Library General
|
| /tools/bpf/bpftool/Documentation/ |
| D | bpftool-iter.rst | 50 with each map element, do checking, filtering, aggregation,
|
| /tools/testing/selftests/cgroup/ |
| D | memcg_protection.m | 79 % XXX here I do parallel reclaim of all siblings
|
1234