Lines Matching +full:reset +full:- +full:trace

1 Demonstrations of reset-trace, for Linux bcc/BPF.
4 You will probably never need this tool. If you kill -9 a bcc tool (plus other
6 left in a semi-enabled state. It's not as bad as it sounds: there may just be
8 used to clean up the tracing state, and reset and disable active tracing.
16 a note is printed. All tracing files can be reset with -F for force, but this
21 # ./reset-trace.sh
27 You can use -v to see what it does:
29 # ./reset-trace.sh -v
34 Checking /sys/kernel/debug/tracing/trace
51 Tracing 317 functions for "bash:r*"... Hit Ctrl-C to end.
105 I've traced 317 functions using funccount, and when I hit Ctrl-C, funccount is
109 Linux 4.9.0-rc1-virtual (bgregg-xenial-bpf-i-xxx) 	10/18/2016 	_x86_64_	(8 CPU)
112 10:00:34 PM 60004      3277    0.00    0.98    0.00    0.98     0  redis-server
122 funccount looks a lot like it's in an infinite loop (I can use a stack-sampling
124 you read this. But right now it's a good example of needing reset-trace.
131 Ok, so the process is now gone, but it did leave tracing in a semi-enabled
132 state. Using reset-trace:
134 # ./reset-trace.sh -v
139 Needed to reset /sys/kernel/debug/tracing/uprobe_events
160 Checking /sys/kernel/debug/tracing/trace
176 # ./reset-trace.sh
177 Needed to reset /sys/kernel/debug/tracing/uprobe_events
182 # ./reset-trace.sh -q
186 Here is an example of reset-trace detecting an unrelated tracing session:
188 # ./reset-trace.sh 
189 …debug/tracing/set_ftrace_filter isn't set as expected. Not resetting (-F to force, -v for verbose).
193 # ./reset-trace.sh -v
198 Checking /sys/kernel/debug/tracing/trace
201 …debug/tracing/set_ftrace_filter isn't set as expected. Not resetting (-F to force, -v for verbose).
227 it's not in the default state -- something is either using it or has left it
228 enabled. These files can be reset with -F, but that may break other tools that
232 Use -h to print the USAGE message:
234 # ./reset-trace.sh -h
235 USAGE: reset-trace [-Fhqv]
236                  -F             # force: reset all tracing files
237                  -v             # verbose: print details while working
238                  -h             # this usage message
239                  -q             # quiet: no output
241        reset-trace              # disable semi-enabled tracing