Searched refs:what (Results 1 – 14 of 14) sorted by relevance
| /tools/usb/usbip/ |
| D | COPYING | 46 want its recipients to know that what they have is not the original, so
77 Whether that is true depends on what the Program does.
226 This section is intended to make thoroughly clear what is believed to
293 <one line to give the program's name and a brief idea of what it does.>
339 library. If this is what you want to do, use the GNU Library General
|
| D | README | 81 In another terminal, let's look up what USB devices are physically
|
| D | INSTALL | 120 you can set and what kinds of files go in them.
|
| /tools/power/cpupower/bench/ |
| D | README-BENCH | 13 - Possibly Real time priority testing? -> what happens if there are
|
| /tools/objtool/Documentation/ |
| D | stack-validation.txt | 73 what it looks like instead:
211 Here are some examples of common warnings reported by objtool, what
334 Also see the above section for .S file errors for more information what
|
| /tools/perf/ |
| D | design.txt | 71 The 'config' field specifies what the counter should count. It
82 If 'raw_type' is 0, then the 'type' field says what kind of counter
176 has irq_period > 0. The record_type controls what data is recorded on each
|
| /tools/perf/Documentation/ |
| D | examples.txt | 120 allocations - to see precisely what kind of page allocations there
|
| D | intel-pt.txt | 90 a branch sample is synthesized for every single branch. To get an idea what
118 which results in the decoder not knowing what code was executed.
375 interesting happens, we can stop it and grab a snapshot of what was going on
550 have memory limits imposed upon them. That affects what buffer sizes they can
688 are quite important. Users must know if what they are seeing is a complete
|
| D | perf-script-perl.txt | 108 every event in a trace, which covers 90% of what you need to know to
|
| D | perf-script-python.txt | 258 that's what works for now).
504 every event in a trace, which covers 90% of what you need to know to
|
| D | perf-config.txt | 181 'perf.data' file header to, at analysis time find what is needed to do
|
| D | perf-record.txt | 72 what the configuration parameters are, as long as their semantic is
|
| /tools/scripts/ |
| D | utilities.mak | 13 # what should replace a newline when escaping
|
| /tools/perf/util/ |
| D | probe-event.c | 1187 static int parse_line_num(char **ptr, int *val, const char *what) in parse_line_num() argument
1194 semantic_error("'%s' is not a valid number.\n", what); in parse_line_num()
|