kdb: use ktime_get_mono_fast_ns() instead of ktime_get_ts()
authorBaolin Wang <baolin.wang@linaro.org>
Mon, 29 Jan 2018 02:22:51 +0000 (10:22 +0800)
committerJason Wessel <jason.wessel@windriver.com>
Thu, 1 Feb 2018 03:31:09 +0000 (21:31 -0600)
commit40b90efeae9be8702d387dbcbb3aadc57033d4db
tree08dd529110a106de84a75777b056134757e5b74f
parent33f765f698895527acd69faf5d54ab07f02683ff
kdb: use ktime_get_mono_fast_ns() instead of ktime_get_ts()

The kdb code will print the monotonic time by ktime_get_ts(), but
the ktime_get_ts() will be protected by a sequence lock, that will
introduce one deadlock risk if the lock was already held in the
context from which we entered the debugger.

Thus we can use the ktime_get_mono_fast_ns() to get the monotonic
time, which is NMI safe access to clock monotonic. Moreover we can
remove the 'struct timespec', which is not y2038 safe.

Signed-off-by: Baolin Wang <baolin.wang@linaro.org>
Reviewed-by: Daniel Thompson <daniel.thompson@linaro.org>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
kernel/debug/kdb/kdb_main.c