mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-11-26 13:44:15 +08:00
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>
This commit is contained in:
parent
33f765f698
commit
40b90efeae
@ -2512,10 +2512,10 @@ static int kdb_kill(int argc, const char **argv)
|
||||
*/
|
||||
static void kdb_sysinfo(struct sysinfo *val)
|
||||
{
|
||||
struct timespec uptime;
|
||||
ktime_get_ts(&uptime);
|
||||
u64 uptime = ktime_get_mono_fast_ns();
|
||||
|
||||
memset(val, 0, sizeof(*val));
|
||||
val->uptime = uptime.tv_sec;
|
||||
val->uptime = div_u64(uptime, NSEC_PER_SEC);
|
||||
val->loads[0] = avenrun[0];
|
||||
val->loads[1] = avenrun[1];
|
||||
val->loads[2] = avenrun[2];
|
||||
|
Loading…
Reference in New Issue
Block a user