From: Thomas Gleixner <tglx@linutronix.de>
To: Prarit Bhargava <prarit@redhat.com>
Cc: Mark Salyzyn <salyzyn@android.com>,
LKML <linux-kernel@vger.kernel.org>,
rjw@rjwysocki.net, len.brown@intel.com, pavel@ucw.cz,
linux-pm@vger.kernel.org, a.zummo@towertech.it,
alexandre.belloni@free-electrons.com, linux-rtc@vger.kernel.org,
andy.shevchenko@gmail.com, Mark Salyzyn <salyzyn@google.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Thierry Strudel <tstrudel@google.com>,
John Stultz <john.stultz@linaro.org>,
Richard Cochran <richardcochran@gmail.com>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
Kees Cook <keescook@chromium.org>, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v2 1/4] time: rtc-lib: Add rtc_show_time(const char *prefix_msg)
Date: Wed, 19 Jul 2017 14:28:31 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1707191426060.2286@nanos> (raw)
In-Reply-To: <f50dbf47-d1dc-5e51-fdcd-0318c2ab93cd@redhat.com>
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
next prev parent reply other threads:[~2017-07-19 12:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 21:19 [PATCH v2 1/4] time: rtc-lib: Add rtc_show_time(const char *prefix_msg) Mark Salyzyn
2017-07-18 21:52 ` Thomas Gleixner
2017-07-18 22:06 ` Mark Salyzyn
2017-07-18 22:35 ` Thomas Gleixner
2017-07-18 23:25 ` Mark Salyzyn
2017-07-19 7:23 ` Thomas Gleixner
2017-07-19 12:03 ` Prarit Bhargava
2017-07-19 12:28 ` Thomas Gleixner [this message]
2017-07-19 14:28 ` Prarit Bhargava
2017-07-19 18:13 ` Mark Salyzyn
2017-07-20 8:20 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1707191426060.2286@nanos \
--to=tglx@linutronix.de \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=andy.shevchenko@gmail.com \
--cc=john.stultz@linaro.org \
--cc=keescook@chromium.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=prarit@redhat.com \
--cc=richardcochran@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=salyzyn@android.com \
--cc=salyzyn@google.com \
--cc=tstrudel@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox