From: Lei Wen <leiwen@marvell.com>
To: John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Stephen Boyd <sboyd@codeaurora.org>,
Andrew Morton <akpm@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
Michael Opdenacker <michael.opdenacker@free-electrons.com>,
Joe Perches <joe@perches.com>, Tejun Heo <tj@kernel.org>,
Petr Mladek <pmladek@suse.cz>, <linux-kernel@vger.kernel.org>,
<leiwen@marvell.com>
Subject: [PATCH 0/3] switch printk timestamp to use booting time
Date: Fri, 4 Apr 2014 11:18:39 +0800 [thread overview]
Message-ID: <1396581522-3309-1-git-send-email-leiwen@marvell.com> (raw)
It is very common to have many processor to run over the same machine
but run different OS actually, so that timestamp alignment is key
to do the right debugging when find something wrong.
Linux adopt schedule clock stopped, so that printk timestamp would get
during suspend period which break such assumption in the old days.
So this patch set is supposed to recover such behavior again.
BTW, I am not sure whether we could add additional member in printk
log structure, so that we could print out two piece of log with
one including suspend time, while another not?
Lei Wen (3):
time: create __get_monotonic_boottime for WARNless calls
timekeeping: move clocksource init to the early place
printk: using booting time as the timestamp
include/linux/time.h | 2 ++
init/main.c | 1 +
kernel/printk/printk.c | 4 ++--
kernel/time/timekeeping.c | 55 ++++++++++++++++++++++++++++++++++++-----------
4 files changed, 48 insertions(+), 14 deletions(-)
--
1.8.3.2
next reply other threads:[~2014-04-04 3:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 3:18 Lei Wen [this message]
2014-04-04 3:18 ` [PATCH 1/3] time: create __get_monotonic_boottime for WARNless calls Lei Wen
2014-04-04 3:18 ` [PATCH 2/3] timekeeping: move clocksource init to the early place Lei Wen
2014-04-04 3:18 ` [PATCH 3/3] printk: using booting time as the timestamp Lei Wen
2014-04-04 21:55 ` John Stultz
2014-04-05 8:01 ` Peter Zijlstra
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=1396581522-3309-1-git-send-email-leiwen@marvell.com \
--to=leiwen@marvell.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.opdenacker@free-electrons.com \
--cc=pmladek@suse.cz \
--cc=rostedt@goodmis.org \
--cc=sboyd@codeaurora.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
/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
all inboxes | Powered by JetHome®