Re: [PATCH 0/2] printk, Add printk.clock kernel parameter [v2]

[Thomas Gleixner]

On Wed, 13 Jan 2016, Prarit Bhargava wrote:
> This patchset introduces additional NMI safe timekeeping functions and the
> kernel parameter printk.clock=[local|boot|real|tai] allowing a
> user to specify an adjusted clock to use with printk timestamps.  The
> hardware clock, or the existing functionality, is preserved by default.

You still fail to explain WHY we need a gazillion of different clocks
here.

What's the problem with using the fast monotonic clock instead of local_clock
and be done with it? I really don't see the point why we would need
boot/real/tai and all the extra churn in the fast clock.

Thanks,

	tglx