diff options
author | 2023-05-26 18:41:36 -0700 | |
---|---|---|
committer | 2023-06-19 16:25:27 -0700 | |
commit | d3b62ace0f097f1d863fb6c41df3c61503e4ec9e (patch) | |
tree | 7a7d05ca38c1d9e0731aca9fc2e6c8a90c3470d8 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | watchdog/hardlockup: remove softlockup comment in touch_nmi_watchdog() (diff) | |
download | wireguard-linux-d3b62ace0f097f1d863fb6c41df3c61503e4ec9e.tar.xz wireguard-linux-d3b62ace0f097f1d863fb6c41df3c61503e4ec9e.zip |
watchdog/buddy: cleanup how watchdog_buddy_check_hardlockup() is called
In the patch ("watchdog/hardlockup: detect hard lockups using secondary
(buddy) CPUs"), we added a call from the common watchdog.c file into the
buddy. That call could be done more cleanly. Specifically:
1. If we move the call into watchdog_hardlockup_kick() then it keeps
watchdog_timer_fn() simpler.
2. We don't need to pass an "unsigned long" to the buddy for the timer
count. In the patch ("watchdog/hardlockup: add a "cpu" param to
watchdog_hardlockup_check()") the count was changed to "atomic_t"
which is backed by an int, so we should match types.
Link: https://lkml.kernel.org/r/20230526184139.6.I006c7d958a1ea5c4e1e4dc44a25596d9bb5fd3ba@changeid
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Suggested-by: Petr Mladek <pmladek@suse.com>
Reviewed-by: Petr Mladek <pmladek@suse.com>
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Nicholas Piggin <npiggin@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions