| /tools/perf/util/ |
| A D | genelf_debug.c | 59 size_t be_sz = be->max_sz; in buffer_ext_add()
63 memcpy(be->data + be->cur_pos, addr, sz); in buffer_ext_add()
64 be->cur_pos += sz; in buffer_ext_add()
77 be->data = tmp; in buffer_ext_add()
78 be->max_sz = be_sz; in buffer_ext_add()
86 be->data = NULL; in buffer_ext_init()
87 be->cur_pos = 0; in buffer_ext_init()
88 be->max_sz = 0; in buffer_ext_init()
94 zfree(&be->data); in buffer_ext_exit()
100 return be->cur_pos; in buffer_ext_size()
[all …]
|
| /tools/testing/selftests/tc-testing/creating-testcases/ |
| A D | AddingTestCases.txt | 8 User-defined tests should be added by defining a separate JSON file. This
17 files you create in these directories will automatically be included.
25 will be used by python. So the match pattern will be a python regular
26 expression, but should be written using json syntax.
48 This list can be empty.
49 Each command can be a string to be executed, or a list consisting
53 will be expected.
59 verifyCmd should be "$TC actions show action gact"
69 This list can be empty.
70 Each command can be a string to be executed, or a list consisting
[all …]
|
| /tools/testing/selftests/tc-testing/creating-plugins/ |
| A D | AddingPlugins.txt | 11 The plugin can be used to add functionality to the test framework,
14 - adding commands to be run before and/or after the test suite
15 - adding commands to be run before and/or after the test cases
17 - ability to alter the command to be run in any phase:
43 This method takes a testcount (number of tests to be run) and
44 testidlist (array of test ids for tests that will be run). This is
46 rest of the tests must be skipped. The info is stored in the object,
51 co-processes) then that other tap output can be generated in the
58 test to be attempted. It can use this info when outputting
71 the execution stage and a string which is the actual command to be
[all …]
|
| /tools/perf/Documentation/ |
| A D | itrace.txt | 34 for instructions events can be specified in units of:
43 transactions events can be specified.
46 instructions or transactions events can be specified.
48 Similar to options g and l, size may also be specified for options G and L.
59 The 'e' option may be followed by flags which affect what errors will or
60 will not be reported. Each flag must be preceded by either '+' or '-'.
65 If supported, the 'd' option may be followed by flags which affect what
66 debug messages will or will not be logged. Each flag must be preceded
72 If supported, the 'q' option may be repeated to increase the effect.
|
| A D | perf-ftrace.txt | 45 normally don't - this option allows the latter to be run in
51 be provided as a comma separated list with no space like: 0,1.
80 be a number with appended unit character - B/K/M/G.
88 function (or a glob pattern). Multiple functions can be given
90 can be a glob pattern. It will be passed to 'set_ftrace_filter'
96 argument. Like -T option, this can be used more than once to
97 specify multiple functions (or glob patterns). It will be
180 The function argument also can be a glob pattern. It will be passed
193 can be used more than once to specify multiple functions. It will be
201 can be used more than once to specify multiple functions. It will be
[all …]
|
| A D | perf-list.txt | 78 address should be. The 'p' modifier can be specified multiple times:
111 it can be encoded in a per processor specific way.
136 raw encoding of 0x1A8 can be used:
149 configuration parameters can be seen with:
164 EventSelect bits have to be specified via bits 32-35 as can be seen with:
194 be specified as
277 also be supplied. For example:
319 errors. Event groups can be specified using { }.
330 be measured.
334 The nmi watchdog can be disabled as root with
[all …]
|
| A D | perf-dlfilter.txt | 18 dynamically loaded shared object file. Arguments can be passed using --dlarg
44 If implemented, 'start' will be called at the beginning, before any
46 or return a negative error code. '*data' can be assigned for use by other
50 If implemented, 'stop' will be called at the end, after any calls to
56 If implemented, 'filter_event' will be called for each sample event.
107 __u8 addr_correlates_sym; /* True => resolve_addr() can be called */
122 'size' can be used to determine their presence at run time.
145 file is loaded. The functions can be called by 'filter_event' or
212 __u8 filtered; /* true if this sample event will be filtered out */
293 it may be necessary to rebuild the .so. Also there may be unexpected results
[all …]
|
| A D | perf-record.txt | 29 Select the PMU event. Selection can be:
203 The <term> can be one of:
209 The <operator> can be one of:
212 The <value> can be one of:
279 Fail if the specified frequency can't be used.
543 must be an AUX area event. Samples on other events will be created containing
555 switch events will be enabled automatically, which can be suppressed by
620 callchains will be collected.
733 events cannot be mixed together. The latter must be used with the -e
735 can be grouped using the {} notation.
[all …]
|
| A D | perf-arm-spe.txt | 91 should be set to avoid collisions.
102 be weighted accordingly.
113 The ARM_SPE_PMU config must be set to build as either a module or statically.
124 disabled (or isn't required to be disabled) but the SPE PMU still doesn't show in
126 ACPI or DT. In this case no warning will be printed by the driver.
158 Only some events can be filtered on; these include:
203 Memory access details are also stored on the samples and this can be viewed with:
218 assigning PIDs to kernel samples. For userspace sampling this can be ignored.
227 SPE has events that can be counted on core PMUs. These are prefixed with
236 first when context switching. For that reason it may be better to open the PMU
[all …]
|
| /tools/testing/selftests/net/forwarding/ |
| A D | README | 7 Unfortunately, these namespaces can not be used with actual switching
8 ASICs, as their ports can not be migrated to other network namespaces
12 However, a similar kind of flexibility can be achieved by using VRFs and
41 These tests are written with switch ASICs in mind, but they can be run
53 o Where possible, tests shall be written so that they can be reused by
55 o Checks shall be added to lib.sh for any external dependencies.
56 o Code shall be checked using ShellCheck [1] prior to submission.
65 various ways. A number of these variables can be overridden. The way these
72 Any of these variables can be overridden. Notably net/forwarding/lib.sh and
80 way to pass it through the environment. Its value can instead be given as
[all …]
|
| A D | bridge_vlan_aware.sh | 115 local mac=de:ad:be:ef:13:37
121 bridge fdb add de:ad:be:ef:13:37 dev $swp1 master extern_learn vlan 1
123 bridge fdb show brport $swp1 | grep -q de:ad:be:ef:13:37
131 bridge fdb show brport $swp1 | grep -q de:ad:be:ef:13:37
136 bridge fdb show brport $swp2 | grep -q de:ad:be:ef:13:37
141 bridge fdb del de:ad:be:ef:13:37 dev $swp2 master vlan 1 &> /dev/null
142 bridge fdb del de:ad:be:ef:13:37 dev $swp1 master vlan 1 &> /dev/null
147 local mac=de:ad:be:ef:13:37
200 local mac=de:ad:be:ef:13:37
|
| /tools/testing/selftests/arm64/ |
| A D | README | 5 completely when env-variable ARCH is found to be different than 'arm64'
8 - Holding true the above, ARM64 KSFT tests can be run within the KSelfTest
19 or, alternatively, only specific arm64/ subtargets can be picked:
24 Further details on building and running KFST can be found in:
|
| /tools/testing/selftests/tc-testing/ |
| A D | README | 21 features. As new tests will be added, config options list will be updated.
23 * All tc-related features being tested must be built in or available as
30 because the kernel did not support a specific feature. (This will be
38 The path to the tc executable that will be most commonly tested can be defined
51 commands being tested must be run as root. The code that enforces
59 to tdc when starting a test run; the veth pair will still be created
88 can be run next. These two stages require any commands run to return
113 the tests to be run. These values are used in the tc commands that will be
147 must be called "SubPlugin" so tdc can find them. They are
181 plugins. It will be detected at run time and invoked at the
[all …]
|
| /tools/testing/selftests/coredump/ |
| A D | README.rst | 8 unexpectedly (e.g. due to segmentation fault), which can be useful for debugging. By default,
9 `coredump` dumps the memory to the file named `core`, but this behavior can be changed by writing a
10 different file name to `/proc/sys/kernel/core_pattern`. Furthermore, `coredump` can be piped to a
11 user-space program by writing the pipe symbol (`|`) followed by the command to be executed to
14 The piped user program may be interested in reading the stack pointers of the crashed process. The
15 crashed process's stack pointers can be read from `procfs`: it is the `kstkesp` field in
27 always be zero
|
| /tools/power/cpupower/ |
| A D | TODO | 9 -> Is by design racy with BIOS, but could be added
10 with a --force option and some "be careful" messages
13 monitor to outside it. This can be given higher
23 This would be ideal as it will not introduce noise in the
|
| /tools/perf/ |
| A D | design.txt | 10 thus be used to profile the code that runs on that CPU.
30 can be used to set the blocking mode, etc.
32 Multiple counters can be kept open at a time, and the counters
33 can be poll()ed.
241 counter to be specific to a task:
267 The 'flags' parameter is currently unused and must be zero.
275 considered to be a group with only 1 member.)
278 only be put onto the CPU if all of the counters in the group can be
294 * Structure of the page that can be mapped via mmap
381 * will be PERF_RECORD_*
[all …]
|
| /tools/testing/selftests/futex/ |
| A D | README | 11 primitives. These can be used as is in user applications or can serve as
12 examples for system libraries. These will likely be added to either a new lib/
23 o Tests should be as self contained as is practical so as to facilitate sharing
27 o Where possible, any helper functions or other package-wide code shall be
36 Test output shall be easily parsable by both human and machine. Title and
46 # FIXME: Perhaps an " INFO: informational message" option would be
48 # there may be multiple ERROR or FAIL messages
|
| /tools/testing/selftests/net/packetdrill/ |
| A D | tcp_eor_no-coalesce-retrans.pkt | 4 // will not be coalesce into the same skb.
35 // This chunk should not be appended to the skbs created for the previous chunk.
42 // The 9 remaining 400B chunks should be sent as individual packets.
52 // The last 10KB chunk should be sent separately.
61 // retransmissions should be sent out as individual packets.
|
| A D | tcp_timestamping_server.pkt | 40 // SCM_TSTAMP_SCHED for the first chunk should be received almost immediately
58 // SCM_TSTAMP_SND for the first chunk should be received almost immediately
76 // SCM_TSTAMP_SCHED for the second chunk should be received almost immediately
94 // SCM_TSTAMP_SND for the second chunk should be received almost immediately
112 // SCM_TSTAMP_ACK for the first chunk should be received at t=20ms.
129 // SCM_TSTAMP_ACK for the second chunk should be received at t=30ms.
|
| /tools/testing/selftests/drivers/net/ |
| A D | README.rst | 17 (for example) can be run under ``virtme-ng`` like the core networking selftests.
23 The netdevice against which tests will be run must exist, be running
24 (in UP state) and be configured with an IP address.
33 and a real device. SW-only tests should instead be placed in net/ or
39 The variables can be set in the environment or by creating a net.config
57 Name of the netdevice against which the test should be executed.
58 When empty or not set software devices will be used.
77 It should be possible to add a new method without modifying any of
|
| /tools/testing/selftests/drivers/net/mlxsw/spectrum/ |
| A D | vxlan_flooding_ipv6.sh | 229 $MZ -6 $h1 -q -p 64 -b de:ad:be:ef:13:37 -t ip -c 1
245 $MZ -6 $h1 -q -p 64 -b de:ad:be:ef:13:37 -t ip -c 1
259 $MZ -6 $h1 -q -p 64 -b de:ad:be:ef:13:37 -t ip -c 1
273 $MZ -6 $h1 -q -p 64 -b de:ad:be:ef:13:37 -t ip -c 1
284 $MZ -6 $h1 -q -p 64 -b de:ad:be:ef:13:37 -t ip -c 1
293 $MZ -6 $h1 -q -p 64 -b de:ad:be:ef:13:37 -t ip -c 1
302 $MZ -6 $h1 -q -p 64 -b de:ad:be:ef:13:37 -t ip -c 1
311 $MZ -6 $h1 -q -p 64 -b de:ad:be:ef:13:37 -t ip -c 1
320 $MZ -6 $h1 -q -p 64 -b de:ad:be:ef:13:37 -t ip -c 1
|
| /tools/bpf/bpftool/Documentation/ |
| A D | bpftool-prog.rst | 75 match several programs which will all be shown.
93 will be disassembled and printed to standard output in human-readable
98 will all be dumped. However, if **file** or **visual** is specified,
101 If **file** is specified, the binary image will instead be written to
108 If the programs have line_info available, the source line will be
110 column will also be displayed.
119 **opcodes** controls if raw opcodes will be printed.
123 be displayed.
142 **offload_dev** *NAME* is specified program will be loaded onto given
206 default of 32 kB should be more than enough for most cases.
[all …]
|
| A D | bpftool-feature.rst | 42 To enable them and run all probes, the **full** keyword should be used.
46 be included in a C header file, for example. If, additionally, **prefix**
47 is used to define a *PREFIX*, the provided string will be used as a prefix
48 to the names of the macros: this can be used to avoid conflicts on macro
51 Keyword **kernel** can be omitted. If no probe target is specified, probing
70 List items known to bpftool. These can be BPF program types
76 can be used in scripts to iterate over BPF types or helpers.
|
| /tools/testing/selftests/devices/probe/boards/ |
| A D | google,spherion.yaml | 5 # file will be automatically used when the test is run on that machine.
10 # Every controller needs to be uniquely identified on the platform. To achieve
11 # this, several optional keys can be used:
16 # sibling controllers. In this case, dt-mmio can't be used, and this property
24 # controller. A device might be a leaf device or another controller (see
38 # interfaces in that device that should be bound to a driver.
|
| /tools/memory-model/Documentation/ |
| A D | locking.txt | 49 then both r0 and r1 must be set to the value 1. This also has the
51 value of r1 must also be equal to 1. In contrast, the weaker rule would
59 lock will not see any changes that will be made by any CPU after it
81 mylock before CPU1(), then both r0 and r1 must be set to the value 0.
83 to 0, then the final value of r0 must also be equal to 0. In contrast,
141 be ordered before the READ_ONCE() from data, thus solving the first
142 problem. The smp_store_release() guarantees that its store will be
183 Counter-intuitive though it might be, it is quite possible to have
184 the final value of r0 be 1, the final value of z be 2, and the final
189 Ordering can be extended to CPUs not holding the lock by careful use
[all …]
|