[lkml]   [2013]   [Jun]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] proc: make high precision system boot time available
On 30 June 2013 16:10, Kay Sievers <> wrote:
> On Sat, Jun 29, 2013 at 10:53 PM, Sami Kerola <> wrote:
>> BTW having a way to measure effect of suspend/resume could lead to a
>> way to fix time time distortion.
>> Perhaps there is better alternative to fix user space programs.
>> Unfortunately I do not have either knowledge, or imagination, to come
>> up with any. Fix hints, ideas, and other proposal are most welcome.
> Stuff should just use:
> clock_gettime(CLOCK_BOOTTIME, &ts);
> to get the time in better resolution, and with suspend time taken into account?
> As a general note, the kmsg/printk() time in the raw kernel log is the
> time of the CPU it runs on, especially during early init this time
> might not be in sync across CPUs and stuff jumps event in the very
> same stream on events from the kernel itself:

Thank you Kay,

The clock_gettime(CLOCK_BOOTTIME, &uptime); seems to be exactly what
dmesg needs. A patch to fix dmesg wigging will be sent to util-linux
maillist shortly. Perhaps the dmesg / journald time stamp difference
issue will be fixed someday, but that discussion does not belong to
linux-kernel mailist, so it is time to declare

end of thread.

Sami Kerola

 \ /
  Last update: 2013-06-30 20:01    [W:0.026 / U:6.448 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site