Messages in this thread | | | From | Jiri Olsa <> | Subject | [RFC 0/8] perf tools: Add daemon command | Date | Sat, 12 Dec 2020 11:43:50 +0100 |
| |
hi, we were asked for possibility to be able run record sessions on background, sending the first stab on it to gather more info.
This patchset adds support to configure and run record sessions on background via new 'perf daemon' command.
Please check below the example on usage.
Available also here: git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git perf/daemon
thoughts? ;-)
thanks, jirka
--- Jiri Olsa (8): perf tools: Add debug_set_file function perf tools: Add debug_set_display_time function perf tools: Add config set interface perf daemon: Add daemon command perf daemon: Add signal command perf daemon: Add stop command perf daemon: Allow only one daemon over base directory perf daemon: Set control fifo for session
tools/perf/Build | 3 + tools/perf/Documentation/perf-daemon.txt | 135 +++++++++++++++++ tools/perf/builtin-daemon.c | 916 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ tools/perf/builtin.h | 1 + tools/perf/command-list.txt | 1 + tools/perf/perf.c | 1 + tools/perf/util/config.c | 28 +++- tools/perf/util/config.h | 3 + tools/perf/util/debug.c | 41 ++++- tools/perf/util/debug.h | 3 + 10 files changed, 1124 insertions(+), 8 deletions(-) create mode 100644 tools/perf/Documentation/perf-daemon.txt create mode 100644 tools/perf/builtin-daemon.c
--- Example with that runs 2 record sessions:
# cat config.daemon [daemon] base=/opt/perfdata
[session-1] run = -m 10M -e cycles -o /opt/perfdata/1/perf.data --overwrite --switch-output -a
[session-2] run = -m 20M -e sched:* -o /opt/perfdata/2/perf.data --overwrite --switch-output -a
Default perf config has the same daemon base:
# cat ~/.perfconfig [daemon] base=/opt/perfdata
Starting the daemon:
# perf daemon --config config.daemon
Check sessions:
# perf daemon [1:92187] perf record -m 11M -e cycles -o /opt/perfdata/1/perf.data --overwrite --switch-output -a [2:92188] perf record -m 20M -e sched:* -o /opt/perfdata/2/perf.data --overwrite --switch-output -a
Check sessions with more info:
# perf daemon -v [1:92187] perf record -m 11M -e cycles -o /opt/perfdata/1/perf.data --overwrite --switch-output -a output: /opt/perfdata/1/output control: /opt/perfdata/1/control ack: /opt/perfdata/1/ack [2:92188] perf record -m 20M -e sched:* -o /opt/perfdata/2/perf.data --overwrite --switch-output -a output: /opt/perfdata/2/output control: /opt/perfdata/2/control ack: /opt/perfdata/2/ack
The 'output' file is perf record output for specific session. The 'control' and 'ack' files are perf control files.
Send SIGUSR2 signal to all sessions:
# perf daemon -s signal 12 sent to session '1 [92187]' signal 12 sent to session '2 [92188]'
Send SIGUSR2 signal to session '1':
# perf daemon --signal=1 signal 12 sent to session '1 [364758]'
And check that the perf data dump was trigered:
# cat /opt/perfdata/2/output rounding mmap pages size to 32M (8192 pages) [ perf record: dump data: Woken up 1 times ] [ perf record: Dump /opt/perfdata/2/perf.data.2020120715220385 ]
Stop daemon:
# perf daemon --stop perf daemon is exciting
| |