Lines Matching full:thread
15 2.2.2 Per-thread mode
116 The perf profiles programs with different modes: default mode, per thread
129 This command doesn't specify any options for CPU and thread modes, the
142 than for all threads in the system. The *T1* thread represents the
143 thread context of the 'test_program', whereas *T2* and *T3* are irrelevant
145 the *T1* thread and stored in the ring buffer associated with the CPU on
146 which the *T1* thread is running.
190 T1: Thread 1; T2: Thread 2; T3: Thread 3
191 x: Thread is in running state
195 2.2.2 Per-thread mode
198 By specifying option ``--per-thread`` in perf command, e.g.
202 perf record --per-thread test_program
211 In this mode, a single ring buffer is allocated for the profiled thread;
212 if the thread is scheduled on a CPU, the events on that CPU will be
213 enabled; and if the thread is scheduled out from the CPU, the events on
214 the CPU will be disabled. When the thread is migrated from one CPU to
245 T1: Thread 1
246 x: Thread is in running state
248 Figure 4. Ring buffer for per-thread mode
250 When perf runs in per-thread mode, a ring buffer is allocated for the
251 profiled thread *T1*. The ring buffer is dedicated for thread *T1*, if the
252 thread *T1* is running, the perf events will be recorded into the ring
253 buffer; when the thread is sleeping, all associated events will be
275 options for per-thread mode and per-CPU mode, e.g. the options ``–C 0,2`` and
276 ``––per–thread`` are specified together, the samples are recorded only when
277 the profiled thread is scheduled on any of the listed CPUs.
311 T1: Thread 1; T2: Thread 2; T3: Thread 3
312 x: Thread is in running state
377 T1: Thread 1; T2: Thread 2; T3: Thread 3
378 x: Thread is in running state
642 in the system. For per-thread mode, the perf tool allocates only one
714 T1: Thread 1; T2: Thread 2; T3: Thread 3
715 x: Thread is in running state
804 As we know, the buffers' deployment can be per-thread mode, per-CPU