On Wed, 19 Jul 2017, Prarit Bhargava wrote:
> On 07/19/2017 03:23 AM, Thomas Gleixner wrote:
> > There is another option to remedy this and the dmesg tooling issues:
> >
> > Instead of switching the time stamps in dmesg to a different clock we might
> > as well have an optional secondary timestamp. So instead of:
> >
> > [ 341.590930] wlan0: associated
> >
> > you would get:
> >
> > [ 341.590930] [ sec.usec] wlan0: associated
> >
> > where the second time stamp would be CLOCK_REALTIME/BOOTTIME.
> >
> > That should also solve Prarits problem, hmm?
>
> It would but I would prefer a single time stamp be printed than two. I think
> two timestamps is adding confusion to the output from a end-users point of
> view.
Fair enough. I came up with that idea when I looked at the old thread. The
discussion about tools (e.g. dmesg) dried out at some point and looked
unresolved.
Thanks,
tglx
