Project

General

Profile

Bug #169

Lttng Kernel Module: Timestamp offset invalid on a 32 bit OS

Added by Matthew Khouzam about 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
High
Target version:
Start date:
03/13/2012
Due date:
% Done:

0%

Estimated time:

Description

In the metadata of a kernel trace we have the following clock descriptor:
clock {
name = monotonic;
uuid = "ed4eb84f-b43c-4133-8db8-28203028f97b";
description = "Monotonic Clock";
freq = 1000000000; /* Frequency, in Hz /
/
clock value offset from Epoch is: offset * (1/freq) */
offset = 18445690674791632402;
};

The offset is too high, it should be
clock {
name = monotonic;
uuid = "ed4eb84f-b43c-4133-8db8-28203028f97b";
description = "Monotonic Clock";
freq = 1000000000; /* Frequency, in Hz /
/
clock value offset from Epoch is: offset * (1/freq) */
offset = 1330617403233586776;
};
Like in UST.

Also available in: Atom PDF