From: Qixuan Wu <qixuan.wu@linux.alibaba.com>
To: John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Stephen Boyd <sboyd@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: About dmesg time and uptime
Date: Wed, 21 Mar 2018 01:03:10 +0800 [thread overview]
Message-ID: <5AB13ECE.2090005@linux.alibaba.com> (raw)
Hi All,
I have a doubt in kernel 4.9 about dmesg time and uptime. Would you
please to help to clarify whether it's bug or not.
Below is our log. The dmesg time second is large than uptime second.
[25049978.919097] bond0.700: port 9(veth4e77160) entered forwarding state
[25049978.926455] bond0.700: port 9(veth4e77160) entered forwarding state
[chenggang.qcg@e80g10383 ~]$ cat /proc/uptime
25023128.55 1416627078.34
I found dmesg second is just directly get from tsc (x86 64 platform).
While the uptime is get by a complicated computation.
In my another board running 4.9, uptime is very large than dmesg
second (about 8000 second).
Thanks & Regards
Qixuan Wu
next reply other threads:[~2018-03-20 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 17:03 Qixuan Wu [this message]
2018-03-21 10:14 ` About dmesg time and uptime 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=5AB13ECE.2090005@linux.alibaba.com \
--to=qixuan.wu@linux.alibaba.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@kernel.org \
--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 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.