From: Jiri Olsa <jolsa@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Michael Petlan <mpetlan@redhat.com>,
Ian Rogers <irogers@google.com>,
Stephane Eranian <eranian@google.com>,
Alexei Budankov <abudankov@huawei.com>
Subject: [RFC 0/8] perf tools: Add daemon command
Date: Sat, 12 Dec 2020 11:43:50 +0100 [thread overview]
Message-ID: <20201212104358.412065-1-jolsa@kernel.org> (raw)
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
next reply other threads:[~2020-12-12 10:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 10:43 Jiri Olsa [this message]
2020-12-12 10:43 ` [PATCH 1/8] perf tools: Add debug_set_file function Jiri Olsa
2020-12-15 15:37 ` Arnaldo Carvalho de Melo
2020-12-12 10:43 ` [PATCH 2/8] perf tools: Add debug_set_display_time function Jiri Olsa
2020-12-15 15:37 ` Arnaldo Carvalho de Melo
2020-12-12 10:43 ` [PATCH 3/8] perf tools: Add config set interface Jiri Olsa
2020-12-15 15:41 ` Arnaldo Carvalho de Melo
2020-12-15 19:11 ` Jiri Olsa
2020-12-12 10:43 ` [PATCH 4/8] perf daemon: Add daemon command Jiri Olsa
2020-12-15 15:40 ` Alexei Budankov
2020-12-15 19:43 ` Jiri Olsa
2020-12-16 7:54 ` Alexei Budankov
2020-12-16 8:14 ` Jiri Olsa
2020-12-18 13:25 ` Namhyung Kim
2020-12-18 19:30 ` Jiri Olsa
2020-12-15 15:44 ` Arnaldo Carvalho de Melo
2020-12-15 19:20 ` Jiri Olsa
2020-12-12 10:43 ` [PATCH 5/8] perf daemon: Add signal command Jiri Olsa
2020-12-15 15:45 ` Arnaldo Carvalho de Melo
2020-12-15 19:14 ` Jiri Olsa
2020-12-12 10:43 ` [PATCH 6/8] perf daemon: Add stop command Jiri Olsa
2020-12-15 15:45 ` Arnaldo Carvalho de Melo
2020-12-12 10:43 ` [PATCH 7/8] perf daemon: Allow only one daemon over base directory Jiri Olsa
2020-12-15 15:46 ` Arnaldo Carvalho de Melo
2020-12-15 19:16 ` Jiri Olsa
2020-12-12 10:43 ` [PATCH 8/8] perf daemon: Set control fifo for session Jiri Olsa
2020-12-15 15:47 ` Arnaldo Carvalho de Melo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201212104358.412065-1-jolsa@kernel.org \
--to=jolsa@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=abudankov@huawei.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.