aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWang Qing <[email protected]>2021-06-28 19:34:20 -0700
committerLinus Torvalds <[email protected]>2021-06-29 10:53:46 -0700
commite55fda8cdcba2cb3d5d46ae5fcd5f243f8b70d6e (patch)
tree65e17d8f7b0d15842c426c18e7509e66186bc617
parentb124ac45bda0338f2aa3969e7c135139267f8987 (diff)
doc: watchdog: modify the explanation related to watchdog thread
"watchdog/%u" threads has be replaced by cpu_stop_work. The current description is extremely misleading. Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: Wang Qing <[email protected]> Reviewed-by: Petr Mladek <[email protected]> Cc: "Guilherme G. Piccoli" <[email protected]> Cc: Joe Perches <[email protected]> Cc: Jonathan Corbet <[email protected]> Cc: Kees Cook <[email protected]> Cc: Mauro Carvalho Chehab <[email protected]> Cc: Qais Yousef <[email protected]> Cc: Randy Dunlap <[email protected]> Cc: Santosh Sivaraj <[email protected]> Cc: Stephen Kitt <[email protected]> Cc: Vlastimil Babka <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]>
-rw-r--r--Documentation/admin-guide/lockup-watchdogs.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/admin-guide/lockup-watchdogs.rst b/Documentation/admin-guide/lockup-watchdogs.rst
index 290840c160af..3e09284a8b9b 100644
--- a/Documentation/admin-guide/lockup-watchdogs.rst
+++ b/Documentation/admin-guide/lockup-watchdogs.rst
@@ -39,7 +39,7 @@ in principle, they should work in any architecture where these
subsystems are present.
A periodic hrtimer runs to generate interrupts and kick the watchdog
-task. An NMI perf event is generated every "watchdog_thresh"
+job. An NMI perf event is generated every "watchdog_thresh"
(compile-time initialized to 10 and configurable through sysctl of the
same name) seconds to check for hardlockups. If any CPU in the system
does not receive any hrtimer interrupt during that time the
@@ -47,7 +47,7 @@ does not receive any hrtimer interrupt during that time the
generate a kernel warning or call panic, depending on the
configuration.
-The watchdog task is a high priority kernel thread that updates a
+The watchdog job runs in a stop scheduling thread that updates a
timestamp every time it is scheduled. If that timestamp is not updated
for 2*watchdog_thresh seconds (the softlockup threshold) the
'softlockup detector' (coded inside the hrtimer callback function)