| /tools/testing/selftests/ftrace/test.d/kprobe/ |
| D | kprobe_ftrace.tc | 16 echo > trace
18 grep testprobe trace
19 ! grep '_do_fork <-' trace
23 echo > trace
25 grep testprobe trace
26 grep '_do_fork <-' trace
30 echo > trace
32 ! grep testprobe trace
33 grep '_do_fork <-' trace
38 echo > trace
[all …]
|
| /tools/perf/ |
| D | builtin-trace.c | 54 struct trace { struct
274 struct trace *trace; member
973 struct trace *trace) in thread__fd_path() argument
984 if (!trace->live) in thread__fd_path()
986 ++trace->stats.proc_getname; in thread__fd_path()
999 const char *path = thread__fd_path(arg->thread, fd, arg->trace); in syscall_arg__scnprintf_fd()
1034 if (!arg->trace->vfs_getname) in syscall_arg__scnprintf_filename()
1041 static bool trace__filter_duration(struct trace *trace, double t) in trace__filter_duration() argument
1043 return t < (trace->duration_filter * NSEC_PER_MSEC); in trace__filter_duration()
1046 static size_t __trace__fprintf_tstamp(struct trace *trace, u64 tstamp, FILE *fp) in __trace__fprintf_tstamp() argument
[all …]
|
| /tools/virtio/virtio-trace/ |
| D | README | 1 Trace Agent for virtio-trace
4 Trace agent is a user tool for sending trace data of a guest to a Host in low
8 - write trace data to stdout by using -o option
11 The trace agent operates as follows:
16 4) After the controller of the trace agent receives a start order from a host,
18 5) The read/write threads start to read trace data from ring-buffers and
21 stop to read trace data.
28 Makefile: Makefile of trace agent for virtio-trace
29 trace-agent.c: includes main function, sets up for operating trace agent
30 trace-agent.h: includes all structures and some macros
[all …]
|
| D | Makefile | 4 all: trace-agent
9 trace-agent: trace-agent.o trace-agent-ctl.o trace-agent-rw.o
13 rm -f *.o trace-agent
|
| /tools/lib/lockdep/uinclude/linux/ |
| D | stacktrace.h | 12 static inline void print_stack_trace(struct stack_trace *trace, int spaces) in print_stack_trace() argument
14 backtrace_symbols_fd((void **)trace->entries, trace->nr_entries, 1); in print_stack_trace()
17 #define save_stack_trace(trace) \ argument
18 ((trace)->nr_entries = \
19 backtrace((void **)(trace)->entries, (trace)->max_entries))
|
| /tools/testing/selftests/ftrace/test.d/ftrace/ |
| D | func_profiler.tc | 57 if grep -v -e '^#' -e 'schedule' trace; then
62 if ! grep -e 'schedule' trace > /dev/null; then
63 cat trace
73 if ! grep -v -e '^#' -e 'schedule' trace > /dev/null; then
74 cat trace
|
| D | fgraph-filter-stack.tc | 61 count=`cat trace | grep '()' | grep -v schedule | wc -l`
68 count=`cat trace | grep 'schedule()' | wc -l`
78 count=`cat trace | grep '()' | grep -v schedule | wc -l`
84 count=`cat trace | grep 'schedule()' | wc -l`
|
| D | fgraph-filter.tc | 39 count=`cat trace | grep '()' | grep -v schedule | wc -l`
45 count=`cat trace | grep 'schedule()' | wc -l`
|
| /tools/perf/trace/beauty/ |
| D | pid.c | 4 struct trace *trace = arg->trace; in syscall_arg__scnprintf_pid() local
6 struct thread *thread = machine__findnew_thread(trace->host, pid, pid); in syscall_arg__scnprintf_pid()
|
| /tools/testing/selftests/ftrace/test.d/ |
| D | functions | 2 clear_trace() { # reset trace output
3 echo > trace
6 disable_tracing() { # stop trace recording
10 enable_tracing() { # start trace recording
|
| /tools/testing/selftests/ftrace/test.d/event/ |
| D | toplevel-enable.tc | 31 count=`cat trace | grep -v ^# | wc -l`
42 count=`cat trace | grep -v ^# | wc -l`
53 count=`cat trace | grep -v ^# | wc -l`
|
| D | subsystem-enable.tc | 31 count=`cat trace | grep -v ^# | awk '{ print $5 }' | sort -u | wc -l`
42 count=`cat trace | grep -v ^# | awk '{ print $5 }' | sort -u | wc -l`
53 count=`cat trace | grep -v ^# | awk '{ print $5 }' | sort -u | wc -l`
|
| D | event-enable.tc | 31 count=`cat trace | grep sched_switch | wc -l`
42 count=`cat trace | grep sched_switch | wc -l`
53 count=`cat trace | grep sched_switch | wc -l`
|
| D | event-pid.tc | 38 count=`cat trace | grep sched_switch | wc -l`
52 count=`cat trace | grep sched_switch | grep -v "pid=$mypid" | wc -l`
65 count=`cat trace | grep sched_switch | grep -v "pid=$mypid" | wc -l`
|
| /tools/testing/selftests/powerpc/pmu/ebb/ |
| D | back_to_back_ebbs_test.c | 38 trace_log_counter(ebb_state.trace, ebb_state.stats.ebb_count); in ebb_callee()
53 trace_log_reg(ebb_state.trace, SPRN_SIAR, siar); in ebb_callee()
56 trace_log_reg(ebb_state.trace, SPRN_PMC1, val); in ebb_callee()
59 trace_log_reg(ebb_state.trace, SPRN_MMCR0, val); in ebb_callee()
|
| D | cycles_with_freeze_test.c | 37 trace_log_counter(ebb_state.trace, ebb_state.stats.ebb_count); in ebb_callee()
40 trace_log_reg(ebb_state.trace, SPRN_MMCR0, val); in ebb_callee()
43 trace_log_string(ebb_state.trace, "frozen"); in ebb_callee()
|
| D | ebb.c | 111 trace_log_counter(ebb_state.trace, ebb_state.stats.ebb_count); in standard_ebb_callee()
114 trace_log_reg(ebb_state.trace, SPRN_MMCR0, val); in standard_ebb_callee()
249 trace_buffer_print(ebb_state.trace); in dump_ebb_state()
266 trace_log_reg(ebb_state.trace, SPRN_PMC1 + pmc - 1, val); in count_pmc()
486 ebb_state.trace = trace_buffer_allocate(1 * 1024 * 1024); in ebb_init()
|
| /tools/perf/Documentation/ |
| D | perf-script.txt | 6 perf-script - Read perf.data (created by perf record) and display trace output
19 This command reads the input file and displays the trace recorded.
23 'perf script' to see a detailed trace of the workload that was
27 summarize the raw trace data in various ways (the list of scripts is
39 trace --list' i.e. the actual script name minus any language
71 information on how to write and run your own trace scripts.
80 Display verbose dump of the trace data.
88 Display a list of available trace scripts.
92 Process trace data with the given script ([lang]:script[.ext]).
118 comm, tid, pid, time, cpu, event, trace, ip, sym, dso, addr, symoff,
[all …]
|
| D | perf-trace.txt | 1 perf-trace(1)
6 perf-trace - strace inspired tool
11 'perf trace'
12 'perf trace record'
23 Alternatively, 'perf trace record' can be used as a shortcut to
26 The following options apply to perf trace; options to perf trace record are
59 Filter out events for these pids and for 'trace' itself (comma separated list).
123 man pages for details. The ones that are most useful in 'perf trace'
124 are 'dwarf' and 'lbr', where available, try: 'perf trace --call-graph dwarf'.
164 When tracing pagefaults, the format of the trace is as follows:
[all …]
|
| D | perf-sched.txt | 6 perf-sched - Tool to trace/measure scheduler properties (latencies)
23 'perf sched script' to see a detailed trace of the workload that
28 that mimic the workload based on the events in the trace. These
50 --dump-raw-trace=::
|
| D | perf-lock.txt | 42 --dump-raw-trace::
43 Dump raw trace in ASCII.
|
| /tools/perf/util/scripting-engines/ |
| D | Build | 1 libperf-$(CONFIG_LIBPERL) += trace-event-perl.o
2 libperf-$(CONFIG_LIBPYTHON) += trace-event-python.o
|
| /tools/testing/selftests/ftrace/test.d/trigger/ |
| D | trigger-stacktrace.tc | 36 echo 0 > trace
40 grep "<stack trace>" trace > /dev/null || \
|
| /tools/kvm/kvm_stat/ |
| D | kvm_stat.txt | 15 kvm_stat prints counts of KVM kernel module trace events. These events signify
22 The set of KVM kernel module trace events may be specific to the kernel version
59 'perf'(1), 'trace-cmd'(1)
|
| /tools/testing/selftests/ftrace/test.d/00basic/ |
| D | basic1.tc | 3 test -f README -a -f trace -a -f tracing_on -a -f trace_pipe
|