From: Prarit Bhargava <prarit@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: pmladek@suse.com, olof@lixom.net, akpm@linux-foundation.org,
joelaf@google.com, rostedt@goodmis.org, corbet@lwn.net,
jpoimboe@redhat.com, sergey.senozhatsky@gmail.com,
Jason@zx2c4.com, geert+renesas@glider.be,
gregkh@linuxfoundation.org, cdall@linaro.org, mingo@kernel.org,
hpa@zytor.com, linux-kernel@vger.kernel.org,
sboyd@codeaurora.org, mcgrof@kernel.org,
paulmck@linux.vnet.ibm.com, npiggin@gmail.com,
keescook@chromium.org, peterz@infradead.org,
deepa.kernel@gmail.com, salyzyn@android.com,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:core/printk] printk: Add monotonic, boottime, and realtime timestamps
Date: Tue, 26 Sep 2017 11:43:12 -0400 [thread overview]
Message-ID: <deccbcf1-b415-e649-3b84-55e9d7a06ba9@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1709261732481.2884@nanos>
On 09/26/2017 11:33 AM, Thomas Gleixner wrote:
> On Tue, 26 Sep 2017, Prarit Bhargava wrote:
>> On 09/26/2017 11:26 AM, Thomas Gleixner wrote:
>>> On Tue, 26 Sep 2017, Prarit Bhargava wrote:
>>>
>>>> On 09/26/2017 04:42 AM, tip-bot for Prarit Bhargava wrote:
>>>>> Commit-ID: 310b454a8653ea60d3eb21ce5ab03a282a32fbe1
>>>>> Gitweb: http://git.kernel.org/tip/310b454a8653ea60d3eb21ce5ab03a282a32fbe1
>>>>> Author: Prarit Bhargava <prarit@redhat.com>
>>>>> AuthorDate: Mon, 18 Sep 2017 13:51:00 -0400
>>>>> Committer: Thomas Gleixner <tglx@linutronix.de>
>>>>> CommitDate: Tue, 26 Sep 2017 10:38:07 +0200
>>>>>
>>>>> printk: Add monotonic, boottime, and realtime timestamps
>>>>>
>>>>> printk.time=1/CONFIG_PRINTK_TIME=1 adds a unmodified local hardware clock
>>>>> timestamp to printk messages. The local hardware clock loses time each
>>>>> day making it difficult to determine exactly when an issue has occurred in
>>>>> the kernel log, and making it difficult to determine how kernel and
>>>>> hardware issues relate to each other.
>>>>>
>>>>> Make printk output different timestamps by adding options for no timestamp,
>>>>> the local hardware clock, monotonic clock, boottime clock, and clock
>>>>> realtime. The default clock can be selected via:
>>>>>
>>>>> - Kconfig
>>>>> - Kernel command line parameter
>>>>> - Sysfs file
>>>>>
>>>>> Note, that existing user space tools might be confused by selecting clock
>>>>> realtime, so handle with care.
>>>>
>>>> pmladek found a compile warning due to printk_time being unused. I will post a
>>>> v14 on LKML shortly.
>>>
>>> Errm. I applied v12. where the heck is v13?
>>>
>>> And in the applied patch printk_time is used.....
>>
>> Sorry, my mistake I meant v13.
>>
>> This morning pmladek posted about a warning when when CONFIG_PRINTK is not defined:
>>
>> https://marc.info/?l=linux-doc&m=150642667403344&w=2
>>
>> I'm fixing it now for v13.
>
> Please send a delta patch.
>
Will do.
P.
next prev parent reply other threads:[~2017-09-26 15:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-310b454a8653ea60d3eb21ce5ab03a282a32fbe1@git.kernel.org>
2017-09-26 15:19 ` Prarit Bhargava
2017-09-26 15:26 ` Thomas Gleixner
2017-09-26 15:30 ` Prarit Bhargava
2017-09-26 15:33 ` Thomas Gleixner
2017-09-26 15:43 ` Prarit Bhargava [this message]
2017-08-28 12:21 [PATCH 2/2 v10] " Prarit Bhargava
2017-09-25 19:19 ` [tip:core/printk] " tip-bot for Prarit Bhargava
2017-09-25 23:50 ` Sergey Senozhatsky
2017-09-26 8:38 ` Thomas Gleixner
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=deccbcf1-b415-e649-3b84-55e9d7a06ba9@redhat.com \
--to=prarit@redhat.com \
--cc=Jason@zx2c4.com \
--cc=akpm@linux-foundation.org \
--cc=cdall@linaro.org \
--cc=corbet@lwn.net \
--cc=deepa.kernel@gmail.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=joelaf@google.com \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mingo@kernel.org \
--cc=npiggin@gmail.com \
--cc=olof@lixom.net \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=salyzyn@android.com \
--cc=sboyd@codeaurora.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=tglx@linutronix.de \
/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
Powered by JetHome