Searched refs:tracing (Results 1 – 25 of 27) sorted by relevance
12
| /tools/lib/traceevent/Documentation/ |
| D | libtraceevent-cpus.txt | 6 tep_get_cpus, tep_set_cpus - Get / set the number of CPUs, which have a tracing
21 The _tep_get_cpus()_ function gets the number of CPUs, which have a tracing
24 The _tep_set_cpus()_ function sets the number of CPUs, which have a tracing
26 The _cpu_ argument is the number of CPUs with tracing data.
30 The _tep_get_cpus()_ functions returns the number of CPUs, which have tracing
43 printf("We have tracing data for %d CPUs", tep_get_cpus(tep));
|
| D | libtraceevent-header_page.txt | 45 generate the tracing data, which has no event/header_page. If the kernel is new,
64 printf ("%s kernel is used to generate the tracing data.\n",
|
| D | libtraceevent-parse_head.txt | 44 buf = read_file("/sys/kernel/tracing/events/header_page", &size);
|
| D | libtraceevent-parse_event.txt | 48 buf = read_file("/sys/kernel/tracing/events/ftrace/print/format", &size);
|
| /tools/lib/api/fs/ |
| D | tracing_path.c | 20 static void __tracing_path_set(const char *tracing, const char *mountpoint) in __tracing_path_set() argument
24 mountpoint, tracing); in __tracing_path_set()
26 mountpoint, tracing, "events"); in __tracing_path_set()
|
| /tools/perf/Documentation/ |
| D | perf-ftrace.txt | 17 functionality. It only supports single thread tracing currently and
69 tracing for functions executed from the given function.
77 and disables tracing for function executed from the given function.
|
| D | intel-bts.txt | 32 Currently Intel BTS is limited to per-thread tracing so the --per-thread option
83 perf inject also accepts the --itrace option in which case tracing data is
|
| D | perf-lock.txt | 20 produces the file "perf.data" which contains tracing
|
| D | intel-pt.txt | 41 Another limitation is the performance impact of tracing, something that will
405 branch Enable branch tracing. Branch tracing is enabled by default so to
406 disable branch tracing use 'branch=0'.
423 if branch tracing is enabled, otherwise the address will be zero.
424 Note that fup_on_ptw will work even when branch tracing is disabled.
515 Recording AUX area tracing snapshot
518 Note that "Recording AUX area tracing snapshot" is displayed because the -v
757 e synthesize tracing error events
785 packets. While CBR packets are always recorded when tracing is enabled, power
889 perf inject also accepts the --itrace option in which case tracing data is
|
| D | perf-list.txt | 179 /sys/kernel/debug/tracing, even when perf_event_paranoid is in a relaxed
185 Some PMUs control advanced hardware tracing capabilities, such as Intel PT,
186 that allows low overhead execution tracing. These are described in a separate
|
| D | perf.data-file-format.txt | 240 undecoded hardware tracing information, such as Intel Processor Trace data.
243 * struct auxtrace_index_entry - indexes a AUX area tracing event within a
256 * struct auxtrace_index - index of AUX area tracing events within a perf.data
515 Describes an error in hardware tracing
|
| D | perf-record.txt | 138 - 'start': defines an address at which tracing will begin.
139 - 'stop': defines an address at which tracing will stop.
140 - 'tracestop': defines a region in which tracing will stop.
234 area tracing can be specified.
430 Select AUX area tracing Snapshot Mode. This option is valid only with an
431 AUX area tracing event. Optionally, certain snapshot capturing parameters
|
| D | perf-script-python.txt | 79 - we could enable every event under the tracing/events/syscalls
87 tracing/events/raw_syscalls. These are called for all syscalls; the
322 'perf list' and/or look in /sys/kernel/debug/tracing/events/ for
452 (see /sys/kernel/debug/tracing/events/sched/sched_wakeup/format):
|
| D | examples.txt | 221 in include/tracing/events/kmem.h.
|
| D | perf-kvm.txt | 57 And this command produces a file which contains tracing results of kvm
|
| D | perf-probe.txt | 106 of write it into tracing/[k,u]probe_events.
141 space tracing. Can also be used with --funcs option.
|
| D | perf-script-perl.txt | 58 (see /sys/kernel/debug/tracing/events/sched/sched_wakeup/format):
|
| D | perf-trace.txt | 234 When tracing pagefaults, the format of the trace is as follows:
|
| D | perf-script.txt | 336 Options for decoding instruction tracing data. The options are:
|
| /tools/testing/selftests/ftrace/ |
| D | README | 3 This is a collection of testcases for ftrace tracing feature in the Linux
29 * The working directory of the script is <debugfs>/tracing/.
|
| D | ftracetest | 161 mount -t tracefs nodev /sys/kernel/tracing ||
|
| /tools/testing/selftests/bpf/ |
| D | test_tunnel.sh | 641 > /sys/kernel/debug/tracing/trace
648 grep "reqid 1" /sys/kernel/debug/tracing/trace
650 grep "spi 0x1" /sys/kernel/debug/tracing/trace
652 grep "remote ip 0xac100164" /sys/kernel/debug/tracing/trace
|
| /tools/testing/selftests/ftrace/test.d/ |
| D | functions | 90 # no probes, and tracing on.
|
| /tools/vm/ |
| D | slabinfo.c | 95 int tracing; variable
692 if (tracing) in debug_opt_scan()
694 tracing = 1; in debug_opt_scan()
767 if (tracing && !s->trace) { in slab_debug()
773 if (!tracing && s->trace) in slab_debug()
|
| /tools/virtio/virtio-trace/ |
| D | README | 98 # echo 1 > /sys/kernel/debug/tracing/events/sched/enable
|
12