From: Thomas Gleixner <tglx@linutronix.de>
To: Petr Mladek <pmladek@suse.com>
Cc: Prarit Bhargava <prarit@redhat.com>,
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>,
Tejun Heo <tj@kernel.org>,
Peter Hurley <peter@hurleysoftware.com>,
Vasily Averin <vvs@virtuozzo.com>, Joe Perches <joe@perches.com>
Subject: Re: [PATCH 2/2] printk, Add printk.clock kernel parameter
Date: Fri, 8 Jan 2016 10:04:44 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1601080956330.3575@nanos> (raw)
In-Reply-To: <20160107155236.GO3178@pathway.suse.cz>
On Thu, 7 Jan 2016, Petr Mladek wrote:
> On Thu 2016-01-07 10:38:37, Prarit Bhargava wrote:
> > Heh :) I didn't even think of testing that. I'll have to think about that a
> > bit more. systemd logging must assume boot time/local time. I'll ping those
> > guys with a patch if/when the next version of this gets accepted.
>
> I am not sure how many tools would be affected by this.
I don't see a point in a gazillion of different clocks for printk either.
> An easier solution would be to normalize all times and always save the
> relative time since the boot as it is done now.
Why? What's wrong with simply using the existing ktime_get_mono_fast_ns()
instead of local_clock() and be done with it?
Thanks,
tglx
next prev parent reply other threads:[~2016-01-08 9:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 13:00 [PATCH 0/2] printk, Add a printk.clock kernel parameter Prarit Bhargava
2016-01-06 13:00 ` [PATCH 1/2] kernel, timekeeping, add trylock option to ktime_get_with_offset() Prarit Bhargava
2016-01-06 16:04 ` Jiri Bohac
2016-01-06 16:27 ` Prarit Bhargava
2016-01-06 16:25 ` Petr Mladek
2016-01-06 17:28 ` John Stultz
2016-01-06 17:33 ` John Stultz
2016-01-06 18:06 ` Prarit Bhargava
2016-01-06 18:10 ` Thomas Gleixner
2016-01-06 17:34 ` Thomas Gleixner
2016-01-06 18:09 ` Prarit Bhargava
2016-01-06 18:12 ` Thomas Gleixner
2016-01-06 19:04 ` John Stultz
2016-01-06 19:06 ` Prarit Bhargava
2016-01-06 13:00 ` [PATCH 2/2] printk, Add printk.clock kernel parameter Prarit Bhargava
2016-01-07 14:57 ` Petr Mladek
2016-01-07 15:38 ` Prarit Bhargava
2016-01-07 15:52 ` Petr Mladek
2016-01-08 9:04 ` Thomas Gleixner [this message]
2016-01-06 17:09 ` [PATCH 0/2] printk, Add a " Joe Perches
2016-01-13 12:34 [PATCH 0/2] printk, Add printk.clock kernel parameter [v2] Prarit Bhargava
2016-01-13 12:34 ` [PATCH 2/2] printk, Add printk.clock kernel parameter Prarit Bhargava
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.11.1601080956330.3575@nanos \
--to=tglx@linutronix.de \
--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.com \
--cc=prarit@redhat.com \
--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.