lkml.org 
[lkml]   [2023]   [May]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[PATCH 00/10] watchdog: Cleanup / fixes after buddy series v5 reviews
Date

This patch series attempts to finish resolving the feedback received
from Petr Mladek on the v5 series I posted. Andrew has already landed
v5 so I'm posting this as additional patches.

Probably the only thing that wasn't fully as clean as Petr requested
was the Kconfig stuff. I couldn't find a better way to express it
without a more major overhaul. In the very least, I renamed "NON_ARCH"
to "PERF_OR_BUDDY" in the hopes that will make it marginally better.

Nothing in this series is terribly critical and even the bugfixes are
small. However, it does cleanup a few things that were pointed out in
review.


Douglas Anderson (10):
watchdog/hardlockup: Keep kernel.nmi_watchdog sysctl as 0444 if probe
fails
watchdog/hardlockup: HAVE_NMI_WATCHDOG must implement
watchdog_hardlockup_probe()
watchdog/hardlockup: Don't use raw_cpu_ptr() in
watchdog_hardlockup_kick()
watchdog/hardlockup: In watchdog_hardlockup_check() use cpumask_copy()
watchdog/hardlockup: remove softlockup comment in touch_nmi_watchdog()
watchdog/buddy: Cleanup how watchdog_buddy_check_hardlockup() is
called
watchdog/buddy: Don't copy the cpumask in watchdog_next_cpu()
watchdog/buddy: Simplify the dependency for
HARDLOCKUP_DETECTOR_PREFER_BUDDY
watchdog/hardlockup: Move SMP barriers from common code to buddy code
watchdog/hardlockup: Rename HAVE_HARDLOCKUP_DETECTOR_NON_ARCH to
..._PERF_OR_BUDDY

arch/Kconfig | 3 +-
arch/sparc/kernel/nmi.c | 5 +++
include/linux/nmi.h | 14 ++-------
kernel/watchdog.c | 68 ++++++++++++++++++-----------------------
kernel/watchdog_buddy.c | 28 ++++++++++++++---
lib/Kconfig.debug | 14 ++++-----
6 files changed, 70 insertions(+), 62 deletions(-)

--
2.41.0.rc0.172.g3f132b7071-goog

\
 
 \ /
  Last update: 2023-05-27 03:42    [W:0.205 / U:1.424 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site