Searched refs:syntax (Results 1 – 19 of 19) sorted by relevance
| /tools/testing/selftests/net/mptcp/ |
| A D | pm_nl_ctl.c | 356 syntax(argv); in dsf()
471 syntax(argv); in csf()
597 syntax(argv); in remove_addr()
649 syntax(argv); in announce_addr()
775 syntax(argv); in add_addr()
905 syntax(argv); in del_addr()
910 syntax(argv); in del_addr()
1096 syntax(argv); in get_addr()
1141 syntax(argv); in dump_addrs()
1279 syntax(argv); in add_listener()
[all …]
|
| /tools/perf/Documentation/ |
| A D | perf-probe.txt | 87 syntax is same as PROBE SYNTAX, but NO ARGs.
157 Probe points are defined by following syntax.
177 … the source line number or lazy matching by using 'SRC:ALN' or 'SRC;PTN' syntax, where 'SRC' is th…
188 In the probe syntax, '=', '@', '+', ':' and ';' are treated as a special character. You can use a b…
195 Each probe argument follows below syntax.
209 …e, which takes 3 parameters, bit-width, bit-offset, and container-size (usually 32). The syntax is;
215 Line range is described by following syntax.
221 probe syntax, 'SRC' means the source file path, 'ALN' is start line number,
|
| A D | perf-list.txt | 141 It's also possible to use pmu syntax:
173 It's also possible to use pmu syntax:
185 perf also supports an extended syntax for specifying raw parameters
198 or using extended name syntax
|
| A D | perf-buildid-cache.txt | 79 it follows the same syntax as the DEBUGINFOD_URLS variable, like:
|
| A D | intel-hybrid.txt | 39 To enable a core only event or atom only event, following syntax is supported:
|
| A D | perf-top.txt | 48 syntax see linkperf:perf-record[1].
388 Select a PMU event using libpfm4 syntax (see http://perfmon2.sf.net)
|
| A D | perf-config.txt | 242 it follows the same syntax as the DEBUGINFOD_URLS variable, like:
609 it follows the same syntax as the DEBUGINFOD_URLS variable, like:
|
| A D | perf-record.txt | 658 Uses the same syntax as --event, it will just not be recorded, serving only to
729 Select a PMU event using libpfm4 syntax (see http://perfmon2.sf.net)
830 it follows the same syntax as the DEBUGINFOD_URLS variable, like:
|
| A D | perf.data-file-format.txt | 226 Description of counter groups ({...} in perf syntax)
|
| A D | perf-script.txt | 242 FROM/TO/EVENT/INTX/ABORT/CYCLES/TYPE/SPEC syntax in the following order:
|
| A D | perf-stat.txt | 113 Select a PMU event using libpfm4 syntax (see http://perfmon2.sf.net)
|
| /tools/testing/selftests/x86/bugs/ |
| A D | common.py | 151 cap.syntax = CS_OPT_SYNTAX_ATT
|
| /tools/net/sunrpc/xdrgen/ |
| A D | README | 101 The xdrgen tool can also provide lexical and syntax checking of
122 xdrgen then transforms the parse tree into an abstract syntax tree.
|
| /tools/testing/selftests/tc-testing/creating-testcases/ |
| A D | AddingTestCases.txt | 26 expression, but should be written using json syntax.
|
| /tools/memory-model/ |
| A D | README | 191 Maps from C-like syntax to herd7's internal litmus-test
|
| /tools/bpf/bpftool/Documentation/ |
| A D | bpftool-btf.rst | 66 (**raw**) or C-syntax (**c**) output formats are supported. With C-style
|
| /tools/memory-model/Documentation/ |
| A D | glossary.txt | 176 syntax, for example, "a = b[2]";
|
| A D | simple.txt | 245 an assembler with added syntax and better portability, but the advent of
|
| A D | litmus-tests.txt | 106 to zero suffices for this test, the "{}" syntax is used, which mean the
764 which has the charming effect of requiring different comment syntax in
765 different portions of the litmus test. The C-syntax portions use
|
Completed in 20 milliseconds