Searched refs:trace_pipe (Results 1 – 12 of 12) sorted by relevance
130 char trace_pipe[PATH_MAX]; in do_tracelog() local136 if (!get_tracefs_pipe(trace_pipe)) in do_tracelog()139 trace_pipe_fd = fopen(trace_pipe, "r"); in do_tracelog()
3 test -f README -a -f trace -a -f tracing_on -a -f trace_pipe
14 head -n 1 trace_pipe | grep -q "test input 1"
99 cat /sys/kernel/debug/tracing/trace_pipe &121 cat /sys/kernel/debug/tracing/trace_pipe &143 cat /sys/kernel/debug/tracing/trace_pipe &
141 ftrace. Obviously using grep and awk of trace_pipe is an option as well142 as any script reading trace_pipe.192 /sys/kernel/debug/tracing/trace_pipe in human-readable format although binary201 script that can read trace_pipe from STDIN or a copy of a trace. When used
40 $ cat /sys/kernel/debug/tracing/trace_pipe
40 $ cat /sys/kernel/debug/tracing/trace_pipe > mydump.txt &63 $ cat /sys/kernel/debug/tracing/trace_pipe > mydump.txt &
139 trace_pipe:657 per_cpu/cpu0/trace_pipe659 This is similar to the "trace_pipe" file, and is a consuming672 Like trace_pipe, this is a consuming reader, where multiple1102 When set, reading trace_pipe will not block when polled.1139 trace,trace_pipe. Example::3177 trace_pipe chapter3180 The trace_pipe outputs the same content as the trace file, but3182 trace_pipe is consumed. This means that subsequent reads will be3187 # cat trace_pipe > /tmp/trace.out &[all …]
18 just reads trace_pipe in text and then write it to stdout.
354 The output will appear in the trace and trace_pipe files.526 cat /sys/kernel/debug/tracing/trace_pipe
378 $ cat /sys/kernel/debug/tracing/trace_pipe > out.txt
1208 buffer_size_kb printk_formats trace_pipe2537 And look at the output (note here that we're using 'trace_pipe' instead of2541 root@crownbay:/sys/kernel/debug/tracing# cat trace_pipe