[lkml]   [2017]   [Aug]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v3] printk: Add boottime and real timestamps

On 08/07/2017 01:14 PM, Luis R. Rodriguez wrote:

> Note printk_late_init() is a late_initcall(). This means if the
> printk_time_setting was disabled it will take a while to enable it. Enabling it
> is done at the device_initcall(), so if printk setting is disabled but a user
> enables it with a toggle of the module param there is a period of time during
> which time resolution would be different.

I'm not sure I follow your comment. Could you elaborate with an example of
what you think is going wrong or might be confusing?


> Perhaps for some this is not useful
> information but for others I think this would be very valuable.
> There is also something to say about the time in between initializing access
> to ktime_get_mono_fast_ns(), how early is this reliable?
> All these things could be mentioned on the documentation.
> Luis

 \ /
  Last update: 2017-08-07 20:18    [W:2.024 / U:0.008 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site