Re: [PATCH] proc: make high precision system boot time available

2013-06-30 Thread Sami Kerola
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

Re: [PATCH] proc: make high precision system boot time available

2013-06-30 Thread Kay Sievers
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

Re: [PATCH] proc: make high precision system boot time available

2013-06-29 Thread Sami Kerola
On 29 June 2013 15:23, Eric W. Biederman wrote: > > Nacked-by: "Eric W. Biederman" > > The pach does not solve the problem described. Which might be true, and I am open to better proposals. > Sami Kerola writes: > >> The kernel does not expose precise start time anywhere. Precision of >> sysi

Re: [PATCH] proc: make high precision system boot time available

2013-06-29 Thread Eric W. Biederman
Nacked-by: "Eric W. Biederman" The pach does not solve the problem described. Sami Kerola writes: > The kernel does not expose precise start time anywhere. Precision of > sysinfo() is limited to a second. The /proc/uptime has precision of two > decimals. Neither are good enough when klog m

[PATCH] proc: make high precision system boot time available

2013-06-29 Thread Sami Kerola
The kernel does not expose precise start time anywhere. Precision of sysinfo() is limited to a second. The /proc/uptime has precision of two decimals. Neither are good enough when klog messages are displayed with a log time stamp that is converted to human understandable format, such as ISO-8601