From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Gleixner 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) Message-ID: References: <20170718211930.123077-1-salyzyn@android.com> <8afb372a-3951-6fb9-c0be-82756623061f@android.com> <5016ccc4-7faa-b61e-c0a1-b851620849c7@android.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Return-path: Received: from Galois.linutronix.de ([146.0.238.70]:44774 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751228AbdGSM2w (ORCPT ); Wed, 19 Jul 2017 08:28:52 -0400 In-Reply-To: Sender: linux-pm-owner@vger.kernel.org List-Id: linux-pm@vger.kernel.org To: Prarit Bhargava Cc: Mark Salyzyn , LKML , 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 , "Paul E. McKenney" , Thierry Strudel , John Stultz , Richard Cochran , Nicolas Pitre , Kees Cook , Ingo Molnar , Peter Zijlstra 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