| /tools/usb/usbip/ |
| D | COPYING | 7 of this license document, but changing it is not allowed.
24 this service if you wish), that you receive source code or can get it
40 (2) offer you this license which gives you legal permission to copy,
44 that everyone understands that there is no warranty for this free
53 program proprietary. To prevent this, we have made it clear that any
64 under the terms of this General Public License. The "Program", below,
73 covered by this License; they are outside its scope. The act of
83 notices that refer to this License and to the absence of any warranty;
84 and give any other recipients of the Program a copy of this License
101 parties under the terms of this License.
[all …]
|
| /tools/memory-model/ |
| D | README | 31 this is not absolutely guaranteed.
34 in this release. A compatible model will likely be made available in
37 If you absolutely need to run the model in this particular release,
86 The remainder of this section uses the SB+fencembonceonces.litmus test
110 this litmus test's "exists" clause can not be satisfied.
113 tool itself, but please be aware that this documentation is intended for
149 that during two million trials, the state specified in this litmus
153 for more information. And again, please be aware that this documentation
172 More formally, this file (1) lists the subtypes of the various
180 More formally, this file specifies what executions are forbidden
[all …]
|
| /tools/power/pm-graph/config/ |
| D | custom-timeline-functions.cfg | 5 # and kprobes. It is run like this
62 # Set this to true if you intend to only use the ones defined in this config
67 # Set this to true if you intend to only use the ones defined in this config
78 # The args are pulled directly from the stack using this architecture's registers
88 # function: The symbol name for the function you want probed, this is the
143 # The args are pulled directly from the stack using this architecture's registers
153 # function: The symbol name for the function you want probed, this is the
|
| D | suspend-callgraph.cfg | 7 # and kprobes. It is run like this
11 # NOTE: the output of this test is very large (> 30MB)
81 # limit the callgraph trace to this depth (default: 0 = all)
|
| /tools/memory-model/Documentation/ |
| D | control-dependencies.txt | 5 do not support them. One purpose of this document is therefore to
8 second purpose of this document, namely to help you to avoid breaking
21 can cause other CPUs to see this load as having happened before the load
45 by a store, and this compiler-generated load would not be ordered by
73 Unfortunately, current compilers will transform this as follows at high
91 have been applied. Therefore, if you need ordering in this example,
141 Given this transformation, the CPU is not required to respect the ordering
143 tempting to add a barrier(), but this does not help. The conditional
145 to relying on control dependencies to produce this ordering, you should
160 values were identical, the compiler could pull this store outside of the
[all …]
|
| D | recipes.txt | 35 To see this, compile with a high level of optimization and run
47 There are exceptions to this rule, including:
67 CPU before it released that same lock. Note that this statement is a bit
69 CPU during the time that CPU was holding this same lock". For example,
127 Consider this example:
155 value of r1 be 0. The reason for this surprising outcome is that
204 and another CPU execute a pair of loads from this same pair of variables,
208 In the absence of any ordering, this goal may not be met, as can be seen
210 a number of ways of meeting this goal.
238 in this way to safely initialize of a slab of the stack. Working out
[all …]
|
| D | access-marking.txt | 28 These may be used in combination, as shown in this admittedly improbable
87 that fail to exclude the updates. In this case, it is important to use
95 In theory, plain C-language loads can also be used for this use case.
96 However, in practice this will have the disadvantage of causing KCSAN
107 all that happens is that this cmpxchg() fails, which normally results
109 recurs, this retry will with high probability succeed, so no harm done.
119 In theory, plain C-language loads can also be used for this use case.
120 However, in practice this will have the disadvantage of causing KCSAN
135 Note that this use case requires that the heuristic be able to handle
140 In theory, plain C-language loads can also be used for this use case.
[all …]
|
| D | simple.txt | 9 The options near the beginning of this list are quite simple. The idea
13 Please note that this is a generic guide, and that specific subsystems
34 shared variables. A simple way to achieve this is to define a global lock
38 this lock at a given time, your code will be executed single-threaded.
62 takes this approach for much of its grace-period processing and also
91 we can also achieve this by instead associating the lock with specific
98 The poster boy for this approach is the hash table, where placing a lock
115 scalability. Of course, there is no free lunch: The dark side of this
119 view of this processing and data, in which case something like locking
120 must be used to protect this global view. This is the approach taken
[all …]
|
| D | litmus-tests.txt | 6 versions of this material appeared in a number of LWN articles, including:
66 suffices to avoid this bad outcome:
89 Line 1 starts with "C", which identifies this file as being in the
93 suffix stripped. In this case, the actual test may be found in
100 tests, but this is a bit involved due to the use of multiple parsers.
106 to zero suffices for this test, the "{}" syntax is used, which mean the
109 example that will be presented later in this document.
146 pointer in P0()'s parameter list, this does an unordered store to global
148 is also in P0()'s parameter list, this does a release store to global
181 this directory only:
[all …]
|
| /tools/testing/selftests/rcutorture/doc/ |
| D | rcu-test-image.txt | 20 The next rcutorture build will then incorporate this filesystem into
26 The remainder of this document describes one way to create the
28 kernel. There are probably much better ways of doing this, and this
40 # Empirical evidence says this image will work for 64-bit, but...
|
| /tools/perf/Documentation/ |
| D | perf-inject.txt | 17 this case build-ids (-b option) are read and injected as needed into the event
22 information could make use of this facility.
64 found in the jitdumps files captured in the input perf.data file. Use this option
78 without updating it. Currently this option is supported only by
|
| D | perf-help.txt | 23 up. The 'man' program is used by default for this purpose, but this
|
| D | perf-config.txt | 17 You can manage variables in a configuration file with this command.
70 Given a $HOME/.perfconfig like this:
186 And values of this variable specify percentage colors.
238 The buildid.dir variable can be used to either change this directory
254 Use this to change the default disassembler style to some other value
260 this option lets 'annotate' print a list of assembly code with the source code.
262 If this option is 'true', they can be printed
270 But if this option is 'false', source code of the part
328 When showing source code if this option is 'true',
337 However if this option is 'false', they aren't printed as below.
[all …]
|
| D | perf-lock.txt | 16 and statistics with this 'perf lock' command.
19 between start and end <command>. And this command
|
| D | perf-top.txt | 47 Display this many functions.
51 Only display functions with more events than this.
63 Profile at this frequency. Use 'max' to use the currently maximum
101 Collect data with this RT SCHED_FIFO priority.
104 Annotate this symbol.
251 Note that this feature may not be available on all processors.
260 Enable this to use just the most recent records, which helps in high core count
262 the pausing used in this technique is leading to loss of metadata events such
264 to lots of unknown samples appearing on the UI. Enable this if you are in such
267 this situation, till then, this will remain disabled by default.
[all …]
|
| D | perf-ftrace.txt | 54 normally don't - this option allows the latter to be run in
76 by using this option more than once. The function argument also
83 argument. Like -T option, this can be used more than once to
103 given function (or a glob pattern). Like -G option, this is useful
|
| /tools/perf/util/ |
| D | dsos.c | 131 struct dso *this = rb_entry(*p, struct dso, rb_node); in __dsos__findnew_link_by_longname_id() local
132 int rc = __dso__cmp_long_name(name, id, this); in __dsos__findnew_link_by_longname_id()
141 if (!dso || (dso == this)) in __dsos__findnew_link_by_longname_id()
142 return this; /* Find matching dso */ in __dsos__findnew_link_by_longname_id()
148 rc = dso__cmp_short_name(dso, this); in __dsos__findnew_link_by_longname_id()
|
| /tools/testing/selftests/drivers/net/mlxsw/ |
| D | qos_lib.sh | 65 lldpad will likely configure DCB, and this test will
69 unlikely, passes) of this test.
|
| /tools/lib/traceevent/Documentation/ |
| D | libtraceevent-parse_head.txt | 24 Some old kernels do not have header page info, in this case the
27 this use case, to set the size of a long integer to be used.
70 *Tzvetomir Stoyanov* <tz.stoyanov@gmail.com>, author of this man page.
|
| /tools/testing/selftests/rcutorture/bin/ |
| D | kvm-test-1-run.sh | 175 echo To run this scenario on bare metal: >> $resdir/bare-metal
177 echo " 1." Set your bare-metal build tree to the state shown in this file: >> $resdir/bare-metal
179 echo " 2." Update your bare-metal build tree"'"s .config based on this file: >> $resdir/bare-metal
190 echo " 8." Copy your bare-metal kernel"'"s .config file, overwriting this file: >> $resdir/bare-met…
193 echo " " the rmmod into this file: >> $resdir/bare-metal
|
| /tools/perf/ |
| D | builtin-kmem.c | 794 struct page_stat this = { in evsel__process_page_alloc_event() local
824 this.page = page; in evsel__process_page_alloc_event()
825 pstat = page_stat__findnew_page(&this); in evsel__process_page_alloc_event()
834 pstat = page_stat__findnew_alloc(&this); in evsel__process_page_alloc_event()
843 this.callsite = callsite; in evsel__process_page_alloc_event()
844 pstat = page_stat__findnew_caller(&this); in evsel__process_page_alloc_event()
862 struct page_stat this = { in evsel__process_page_free_event() local
874 this.page = page; in evsel__process_page_free_event()
875 pstat = page_stat__find_page(&this); in evsel__process_page_free_event()
886 this.gfp_flags = pstat->gfp_flags; in evsel__process_page_free_event()
[all …]
|
| /tools/scripts/ |
| D | utilities.mak | 24 # produced during the expansion; this may not be
46 # Use this to escape newlines from within a shell call;
62 # Use this to unescape newlines from within a shell call;
71 # misinterpreted as a brace expansion; this can be
110 # (this is in constrast to a `$(shell ...)' function call,
123 # If the text does not contain a newline, then this function
|
| /tools/testing/kunit/test_data/ |
| D | test_skip_tests.log | 14 ok 2 - example_skip_test # SKIP this test should be skipped
|
| D | test_skip_all_tests.log | 14 ok 2 - example_skip_test # SKIP this test should be skipped
|
| /tools/testing/selftests/ftrace/ |
| D | README | 10 At first, you need to be the root user to run this script.
65 In this case, the test must call exit_untested.
68 In this case, the test must call exit_unsupported.
|