Lines Matching refs:session
35 Not every 'perf record' session is suitable for running under daemon.
36 User need perf session that either produces data on query, like the
37 flight recorder sessions in above example or session that is configured
41 Each session is started with control setup (with perf record --control
77 The stop command stops all the session and the daemon process.
84 --session::
85 Send signal to specific session.
92 --session::
93 Send ping to specific session.
105 session-<NAME>.run:
106 Defines new record session. The value is record's command
109 Each perf record session is run in daemon.base/<NAME> directory.
120 [session-cycles]
123 [session-sched]
150 base: /opt/perfdata/session-cycles
151 output: /opt/perfdata/session-cycles/output
152 control: /opt/perfdata/session-cycles/control
153 ack: /opt/perfdata/session-cycles/ack
156 base: /opt/perfdata/session-sched
157 output: /opt/perfdata/session-sched/output
158 control: /opt/perfdata/session-sched/control
159 ack: /opt/perfdata/session-sched/ack
162 The 'base' path is daemon/session base.
165 The 'output' file is perf record output for specific session.
167 The 'up' number shows minutes daemon/session is running.
170 Make sure control session is online:
177 Send USR2 signal to session 'cycles' to generate perf.data file:
179 # perf daemon signal --session cycles
180 signal 12 sent to session 'cycles [603452]'
182 # tail -2 /opt/perfdata/session-cycles/output
190 signal 12 sent to session 'cycles [603452]'
191 signal 12 sent to session 'sched [603453]'
193 # tail -2 /opt/perfdata/session-cycles/output
196 # tail -2 /opt/perfdata/session-sched/output