On Wed, 15 May 2013 23:21:39 +0200, Jiri Olsa wrote:
> On Tue, May 14, 2013 at 07:13:53PM +0900, Namhyung Kim wrote:
>> From: Namhyung Kim
>>
>> The ftrace record command is for saving raw ftrace buffer contents
>> which can be get from per_cpu/cpuX/trace_pipe_raw.
>>
>> Since ftrace events are
On Wed, 15 May 2013 23:20:52 +0200, Jiri Olsa wrote:
> On Tue, May 14, 2013 at 07:13:53PM +0900, Namhyung Kim wrote:
>> +raw_data = synthesize_raw_data(evsel);
>> +if (raw_data == NULL) {
>> +pr_err("synthesizing raw sample failed\n");
>> +
On Tue, May 14, 2013 at 07:13:53PM +0900, Namhyung Kim wrote:
> From: Namhyung Kim
>
> The ftrace record command is for saving raw ftrace buffer contents
> which can be get from per_cpu/cpuX/trace_pipe_raw.
>
> Since ftrace events are generated very frequently so single thread for
> recording mo
On Tue, May 14, 2013 at 07:13:53PM +0900, Namhyung Kim wrote:
> From: Namhyung Kim
>
> The ftrace record command is for saving raw ftrace buffer contents
> which can be get from per_cpu/cpuX/trace_pipe_raw.
>
> Since ftrace events are generated very frequently so single thread for
> recording mo
From: Namhyung Kim
The ftrace record command is for saving raw ftrace buffer contents
which can be get from per_cpu/cpuX/trace_pipe_raw.
Since ftrace events are generated very frequently so single thread for
recording mostly resulted in buffer overruns. Thus it uses per-cpu
recorder thread to p
5 matches
Mail list logo