Re: [PATCH 4/8] perf data: Add a 'perf' prefix to the generic fields
From: Sebastian Andrzej Siewior
Date: Thu Dec 11 2014 - 13:58:36 EST
On 12/11/2014 07:55 PM, David Ahern wrote:
> On 12/11/14 8:12 AM, Jiri Olsa wrote:
>
>> Before:
>> $ babeltrace ./ctf-data/
>> [03:19:13.962131936] (+0.000001935) cycles: { }, { ip =
>> 0xFFFFFFFF8105443A, tid = 20714, pid = 20714, period = 8 }
>> [03:19:13.962133732] (+0.000001796) cycles: { }, { ip =
>> 0xFFFFFFFF8105443A, tid = 20714, pid = 20714, period = 114 }
>> ...
>>
>> Now:
>> $ babeltrace ./ctf-data/
>> [03:19:13.962131936] (+0.000001935) cycles: { }, { perf_ip =
>> 0xFFFFFFFF8105443A, perf_tid = 20714, perf_pid = 20714, perf_period = 8 }
>> [03:19:13.962133732] (+0.000001796) cycles: { }, { perf_ip =
>> 0xFFFFFFFF8105443A, perf_tid = 20714, perf_pid = 20714, perf_period =
>> 114 }
>> ...
>
> How is babeltrace showing time-of-day for perf-based data files? Is that
> tod when the command is run?
CTF needs an a base offset which we set to 0 because we don't have it.
It then takes the NS timestamp and computes the "time".
> David
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/