Home
last modified time | relevance | path

Searched refs:be (Results 1 – 25 of 171) sorted by relevance

1234567

/tools/perf/util/
Dgenelf_debug.c46 buffer_ext_dump(struct buffer_ext *be, const char *msg) in buffer_ext_dump() argument
50 for (i = 0 ; i < be->cur_pos; i++) in buffer_ext_dump()
51 warnx("%4zu 0x%02x", i, (((char *)be->data)[i]) & 0xff); in buffer_ext_dump()
55 buffer_ext_add(struct buffer_ext *be, void *addr, size_t sz) in buffer_ext_add() argument
58 size_t be_sz = be->max_sz; in buffer_ext_add()
61 if ((be->cur_pos + sz) < be_sz) { in buffer_ext_add()
62 memcpy(be->data + be->cur_pos, addr, sz); in buffer_ext_add()
63 be->cur_pos += sz; in buffer_ext_add()
72 tmp = realloc(be->data, be_sz); in buffer_ext_add()
76 be->data = tmp; in buffer_ext_add()
[all …]
Dtrace-event.c42 int be = tep_is_bigendian(); in trace_event__init2() local
50 tep_set_file_bigendian(pevent, be); in trace_event__init2()
51 tep_set_local_bigendian(pevent, be); in trace_event__init2()
/tools/testing/selftests/tc-testing/creating-testcases/
DAddingTestCases.txt8 User-defined tests should be added by defining a separate JSON file. This
17 files you create in these directories will automatically be included.
18 If you wish to store your custom test cases elsewhere, be sure to run
25 will be used by python. So the match pattern will be a python regular
26 expression, but should be written using json syntax.
39 marked as skipped. This key can be placed anywhere inside the
46 This list can be empty.
47 Each command can be a string to be executed, or a list consisting
48 of a string which is a command to be executed, followed by 1 or
51 will be expected.
[all …]
/tools/testing/selftests/tc-testing/creating-plugins/
DAddingPlugins.txt8 A new plugin should be written in python as a class that inherits from TdcPlugin.
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
16 - adding commands to be run before and/or after the execute phase of 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
[all …]
/tools/perf/Documentation/
Dperf-ftrace.txt41 normally don't - this option allows the latter to be run in
47 be provided as a comma separated list with no space like: 0,1.
54 can be given by using this option more than once. The function
55 argument also can be a glob pattern. It will be passed to
61 this can be used more than once to specify multiple functions
62 (or glob patterns). It will be passed to 'set_ftrace_notrace'
70 This can be used more than once to specify multiple functions.
71 It will be passed to 'set_graph_function' in tracefs.
78 This can be used more than once to specify multiple functions.
79 It will be passed to 'set_graph_notrace' in tracefs.
Dperf-list.txt16 This command displays the symbolic event types which can be selected in the
44 more modifiers. Modifiers allow the user to restrict the events to be
59 The 'p' modifier can be used for specifying how precise the instruction
60 address should be. The 'p' modifier can be specified multiple times:
87 it can be encoded in a per processor specific way.
94 Note: Only the following bit fields can be set in x86 counter
96 OS/user mode flags must be setup using <<EVENT_MODIFIERS, EVENT
110 raw encoding of 0x1A8 can be used:
125 The available PMUs and their raw parameters can be listed with
130 be specified as
[all …]
Dperf-record.txt19 This file can then be inspected later on, using 'perf report'.
29 Select the PMU event. Selection can be:
53 These params can be used to overload default config values per event.
64 - 'name' : User defined event name. Single quotes (') may be used to
73 the value set by the parameters will be overridden.
90 be passed as follows: '\mem:addr[:[r][w][x]]'. len is the range,
103 into an object file first. Optional clang options can be passed via the
109 Note: '--clang-opt' must be placed before '--event/-e'.
112 Each event is separated by commas and the group should be quoted to
137 - 'filter': defines a region that will be traced.
[all …]
Dperf-config.txt40 The file '$(sysconfdir)/perfconfig' can be used to
49 can be used to tell the command to read from or write to only that location.
56 begins. Each variable must be in a section, and have the form
64 newline (double quote `"` and backslash have to be escaped as `\"` and `\\`,
105 # Format can be man, info, web or html
213 Can be overridden by the --proc-map-timeout option on supported
217 Subcommands that can be configured here are 'top', 'report' and 'annotate'.
223 will make the TUI be the default for the 'top' subcommand. Those will be
229 content based identifier that, if available, will be inserted in a
235 and /proc/kcore files to be used at analysis time.
[all …]
Dintel-bts.txt7 Intel BTS could be regarded as a predecessor to Intel PT and has some
15 documentation and consider that the PMU 'intel_bts' can usually be used in
17 recording must also be stipulated i.e. the --per-thread option for
52 This can be further controlled by option --itrace. The --itrace option is
76 This can be further controlled by new option --itrace exactly the same as
/tools/testing/selftests/net/forwarding/
Dbridge_vlan_aware.sh114 local mac=de:ad:be:ef:13:37
120 bridge fdb add de:ad:be:ef:13:37 dev $swp1 master extern_learn vlan 1
122 bridge fdb show brport $swp1 | grep -q de:ad:be:ef:13:37
130 bridge fdb show brport $swp1 | grep -q de:ad:be:ef:13:37
135 bridge fdb show brport $swp2 | grep -q de:ad:be:ef:13:37
140 bridge fdb del de:ad:be:ef:13:37 dev $swp2 master vlan 1 &> /dev/null
141 bridge fdb del de:ad:be:ef:13:37 dev $swp1 master vlan 1 &> /dev/null
DREADME7 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.
/tools/bpf/bpftool/Documentation/
Dbpftool-prog.rst72 default, eBPF will be disassembled and printed to standard
74 controls if raw opcodes should be printed as well.
76 If **file** is specified, the binary image will instead be
79 If **visual** is specified, control flow graph (CFG) will be
80 built instead, and eBPF instructions will be presented with
84 be displayed by default. If **linum** is specified,
85 the filename, line number and line column will also be
90 If *FILE* is specified image will be written to a file,
91 otherwise it will be disassembled and printed to stdout.
93 **opcodes** controls if raw opcodes will be printed.
[all …]
/tools/perf/
Ddesign.txt10 thus be used to profile the code that runs on that CPU.
28 The syscall returns the new fd. The fd can be used via the normal
29 VFS system calls: read() can be used to read the counter, fcntl()
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.
52 pinned : 1, /* must always be on PMU */
113 although there may be variations (e.g., different CPUs might count
145 tracer is available, and event_id values can be obtained from
160 * Bits that can be set in hw_event.read_format to request that
[all …]
/tools/testing/selftests/futex/
DREADME11 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/tc-testing/
DREADME22 features. As new tests will be added, config options list will be updated.
24 * All tc-related features being tested must be built in or available as
31 because the kernel did not support a specific feature. (This will be
39 The path to the tc executable that will be most commonly tested can be defined
52 commands being tested must be run as root. The code that enforces
58 network namespace and creates a veth pair which may be used in those test
60 to tdc when starting a test run; the veth pair will still be created
69 output captured from the failing test will be printed immediately following
76 One run of tests is considered a "test suite" (this will be refined in the
89 can be run next. These two stages require any commands run to return
[all …]
/tools/lib/traceevent/Documentation/
Dlibtraceevent-func_find.txt20 These functions can be used to find function name and start address, by given
21 address. The given address does not have to be exact, it will select the function
28 by given address _addr_. The _addr_ does not have to be exact, it will select the
34 it cannot be found.
37 or 0 in case it cannot be found.
Dlibtraceevent-parse_head.txt21 _buf_ is with _size_, and is supposed to be copied from
25 _tep_parse_header_page()_ function can be called with _size_ equal to 0. The
26 _tep_ context is initialized with default values. The _long_size_ can be used in
27 this use case, to set the size of a long integer to be used.
/tools/power/pm-graph/config/
Dcgskip.txt5 # meant to be skipped in the callgraph trace. It reduces
7 # as leaves with no child calls. It can be editted by
11 # it is found in the config folder. It can be ignored if
/tools/testing/selftests/android/ion/
Dion_test.sh30 echo $TCID: must be run as root >&2
40 echo $TCID: May be CONFIG_ION is not set >&2
/tools/objtool/Documentation/
Dstack-validation.txt12 that stack traces can be reliable.
36 code and debug tools to be able to walk the stack to determine the
41 CONFIG_FRAME_POINTER. For some other architectures they may be
47 But for asm code, the frame setup instructions have to be written by
51 For stack traces based on frame pointers to be reliable, all
55 of the first function will be skipped on the stack trace.
89 functions honor CONFIG_FRAME_POINTER, no functions will ever[*] be
99 An alternative to frame pointers and DWARF, ORC unwind data can be
101 band. So it doesn't affect runtime performance and it can be
110 stack traces need to be reliable (or an unreliable condition needs to
[all …]
/tools/testing/selftests/drivers/net/mlxsw/
Dvxlan_flooding.sh182 flower skip_hw dst_mac de:ad:be:ef:13:37 action pass
245 $MZ $h1 -q -p 64 -b de:ad:be:ef:13:37 -t ip -c 1
259 $MZ $h1 -q -p 64 -b de:ad:be:ef:13:37 -t ip -c 1
271 $MZ $h1 -q -p 64 -b de:ad:be:ef:13:37 -t ip -c 1
283 $MZ $h1 -q -p 64 -b de:ad:be:ef:13:37 -t ip -c 1
294 $MZ $h1 -q -p 64 -b de:ad:be:ef:13:37 -t ip -c 1
303 $MZ $h1 -q -p 64 -b de:ad:be:ef:13:37 -t ip -c 1
312 $MZ $h1 -q -p 64 -b de:ad:be:ef:13:37 -t ip -c 1
/tools/perf/pmu-events/arch/nds32/
Dmapfile.csv6 # Variant[23:20] and Revision [3:0] should be zero.
7 # Version could be used to track version of of JSON file
/tools/perf/pmu-events/
DREADME11 - Regular files with '.json' extension in the name are assumed to be
15 be named 'mapfile.csv' (see below for mapfile format).
22 Architecture standard JSONs must be located in the architecture root
27 should be placed in a separate JSON file - where the file name identifies
30 All the topic JSON files for a CPU model/family should be in a separate
37 The JSONs folder for a CPU model/family may be placed in the root arch
38 folder, or may be placed in a vendor sub-folder under the arch folder
105 The mapfile.csv format is expected to be:
122 always _IGNORED_. It can be empty.
125 CPUID is an arch-specific char string, that can be used
/tools/power/cpupower/
DToDo9 -> Is by design racy with BIOS, but could be added
10 with a --force option and some "be careful" messages
/tools/memory-model/
DREADME14 In addition, the "klitmus7" tool (also externally provided) may be used
16 that litmus test to be exercised within the Linux kernel.
23 Version 7.52 or higher of the "herd7" and "klitmus7" tools must be
62 this litmus test's "exists" clause can not be satisfied.
72 which may then be loaded and run.
190 this limitation can be overcome by modeling the interrupt or
212 atomic_dec_unless_positive(). These can be emulated
215 c. The call_rcu() function is not modeled. It can be
222 d. The rcu_barrier() function is not modeled. It can be
247 This difference would be more of a concern had anyone
[all …]

1234567