From: Prarit Bhargava <prarit@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
John Stultz <john.stultz@linaro.org>,
Xunlei Pang <pang.xunlei@linaro.org>,
Baolin Wang <baolin.wang@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Petr Mladek <pmladek@suse.cz>, Tejun Heo <tj@kernel.org>,
Peter Hurley <peter@hurleysoftware.com>,
Vasily Averin <vvs@virtuozzo.com>, Joe Perches <joe@perches.com>
Subject: Re: [PATCH] printk, allow different timestamps for printk.time
Date: Tue, 26 Jan 2016 15:52:21 -0500 [thread overview]
Message-ID: <56A7DC85.4070603@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1601260929270.3886@nanos>
On 01/26/2016 03:34 PM, Thomas Gleixner wrote:
> Prarit,
>
> On Mon, 25 Jan 2016, Prarit Bhargava wrote:
>> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
>> index 87d40a7..2cf6692 100644
>> --- a/Documentation/kernel-parameters.txt
>> +++ b/Documentation/kernel-parameters.txt
>> @@ -3060,8 +3060,9 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
>> Format: <bool> (1/Y/y=enable, 0/N/n=disable)
>> default: disabled
>>
>> - printk.time= Show timing data prefixed to each printk message line
>> - Format: <bool> (1/Y/y=enable, 0/N/n=disable)
>> + printk.time= Show timestamp prefixed to each printk message line
>> + Format: [0-2] (0 = disable,
>> + 1 = monotonic clock, 2 = real clock)
>
> Doesn't this break systems, which have 'Y/y' on the command line?
I'll fix this by converting to using module_param_cb() and comparing input
strings instead.
Aside: One thing I would also like to add is the ability to also do
printk.time=[real] for real timestamping. I think that's easier to parse for
end users.
>
>> static DEFINE_RAW_SPINLOCK(timekeeper_lock);
>> static struct timekeeper shadow_timekeeper;
>> +static int timekeeping_active;
>>
>> /**
>> * struct tk_fast - NMI safe timekeeper
>> @@ -401,6 +402,16 @@ u64 ktime_get_raw_fast_ns(void)
>> }
>> EXPORT_SYMBOL_GPL(ktime_get_raw_fast_ns);
>>
>> +u64 ktime_get_log_ts(u64 *offset_real)
>> +{
>> + *offset_real = ktime_to_ns(tk_core.timekeeper.offs_real);
>> +
>> + if (timekeeping_active)
>> + return ktime_get_mono_fast_ns();
>> + else
>> + return local_clock();
>
> Just for the record: The fast timekeeper stops across the inner workings of
> suspend/resume. But I think that doesn't matter much.
I've had to debug s/r before using the sysfs interface. It is nice to have that
with a proper timestamp because a lot of the failures are in the driver suspend
and resume paths. I could easily change the options to:
0 = disable
1 = local clock (which along with 0 would maintain the current state of things)
2 = monotonic
3 = real
P.
>
> Otherwise, this looks good now.
>
> Thanks,
>
> tglx
>
>
>
>
next prev parent reply other threads:[~2016-01-26 20:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 15:12 [PATCH] printk, allow different timestamps for printk.time Prarit Bhargava
2016-01-26 20:34 ` Thomas Gleixner
2016-01-26 20:52 ` Prarit Bhargava [this message]
2016-01-27 9:39 ` 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=56A7DC85.4070603@redhat.com \
--to=prarit@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pang.xunlei@linaro.org \
--cc=peter@hurleysoftware.com \
--cc=pmladek@suse.cz \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=vvs@virtuozzo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.