lkml.org 
[lkml]   [2017]   [Aug]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v5 1/2] sched/clock: interface to allow timestamps early in boot
On Mon, 28 Aug 2017, Pasha Tatashin wrote:
> This makes sense. Changing order in timekeeping_init(void) should take care of
> this:
>
> Change to:
>
> void __init timekeeping_init(void)
> {
> /*
> * We must determine boot timestamp before getting current
> * persistent clock value, because implementation of
> * read_boot_clock64() might also call the persistent
> * clock, and a leap second may occur.
> */
>
> read_boot_clock64(&boot);
> ...
> read_persistent_clock64(&now);

No. That's the same crap just the other way round.

s390 can do that, because the boot timestamp is correlated with the
persistent clock. Your's not so much.

Thanks,

tglx

\
 
 \ /
  Last update: 2017-08-28 17:15    [W:0.047 / U:5.308 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site