Chapter 29. Adding and removing tracepoints from a running perf collector without stopping or restarting perf

Procedure

1. Configure the control pipe interface:

   Copy to Clipboard Toggle word wrap

   # mkfifo control ack perf.pipe

2. Run perf record with the control file setup and events you are interested in enabling:

   Copy to Clipboard Toggle word wrap

   # perf record --control=fifo:control,ack -D -1 --no-buffering -e 'sched:*' -o - > perf.pipe

   In this example, declaring 'sched:*' after the -e option starts perf record with scheduler events.

3. In a second terminal, start the read side of the control pipe:

   Copy to Clipboard Toggle word wrap

   # cat perf.pipe | perf --no-pager script -i -

   Starting the read side of the control pipe triggers the following message in the first terminal:

   Copy to Clipboard Toggle word wrap

   Events disabled

4. In a third terminal, enable a tracepoint using the control file:

   Copy to Clipboard Toggle word wrap

   # echo 'enable sched:sched_process_fork' > control

   This command triggers perf to scan the current event list in the control file for the declared event. If the event is present, the tracepoint is enabled and the following message appears in the first terminal:

   Copy to Clipboard Toggle word wrap

   event sched:sched_process_fork enabled

   Once the tracepoint is enabled, the second terminal displays the output from perf detecting the tracepoint:

   Copy to Clipboard Toggle word wrap

   bash 33349 [034] 149587.674295: sched:sched_process_fork: comm=bash pid=33349 child_comm=bash child_pid=34056