On Tue, Dec 15, 2020 at 12:44:08PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Sat, Dec 12, 2020 at 11:43:54AM +0100, Jiri Olsa escreveu:
> > Adding daemon command that allows to run record sessions
> > on background. Each session represents one perf record
> > process and is configured in config file.
> >
> > Example:
> >
> > # 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:
>
> "Check"? You mean that using 'perf daemon' without any args will just
> attach to whatever daemon is running and list the current sessions?
>
> So we can only have one daemon running in a machine?
>
> That seems constraining, perhaps we can give each daemon a name?
as I explained in the other email, the difference is the base path
specified for both daemon and other commands
I made other changes showing line for daemon process itself
with base path:
$ sudo /opt/perf/bin/perf daemon
[690174:daemon] base: /opt/perfdata
[690175:top] perf record -e cycles --switch-output=1m --switch-max-files=6 -a
$ sudo /opt/perf/bin/perf daemon -v
[690174:daemon] base: /opt/perfdata
output: /opt/perfdata/output
lock: /opt/perfdata/lock
up: 268 minutes
[690175:top] perf record -e cycles --switch-output=1m --switch-max-files=6 -a
base: /opt/perfdata/top
output: /opt/perfdata/top/output
control: /opt/perfdata/top/control
ack: /opt/perfdata/top/ack
up: 268 minutes
jirka
