doc: watchdog: modify the doc related to "watchdog/%u"

"watchdog/%u" threads has be replaced by cpu_stop_work.  The current
description is extremely misleading.

Link: https://lkml.kernel.org/r/1619687073-24686-5-git-send-email-wangqing@vivo.com
Signed-off-by: Wang Qing <wangqing@vivo.com>
Reviewed-by: Petr Mladek <pmladek@suse.com>
Cc: "Guilherme G. Piccoli" <gpiccoli@canonical.com>
Cc: Joe Perches <joe@perches.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Kees Cook <keescook@chromium.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Qais Yousef <qais.yousef@arm.com>
Cc: Randy Dunlap <rdunlap@infradead.org>
Cc: Santosh Sivaraj <santosh@fossix.org>
Cc: Stephen Kitt <steve@sk2.org>
Cc: Vlastimil Babka <vbabka@suse.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
Wang Qing 2021-06-28 19:34:24 -07:00 committed by Linus Torvalds
parent e55fda8cdc
commit 256f7a6791

View File

@ -1283,11 +1283,11 @@ This parameter can be used to control the soft lockup detector.
= ================================= = =================================
The soft lockup detector monitors CPUs for threads that are hogging the CPUs The soft lockup detector monitors CPUs for threads that are hogging the CPUs
without rescheduling voluntarily, and thus prevent the 'watchdog/N' threads without rescheduling voluntarily, and thus prevent the 'migration/N' threads
from running. The mechanism depends on the CPUs ability to respond to timer from running, causing the watchdog work fail to execute. The mechanism depends
interrupts which are needed for the 'watchdog/N' threads to be woken up by on the CPUs ability to respond to timer interrupts which are needed for the
the watchdog timer function, otherwise the NMI watchdog — if enabled — can watchdog work to be queued by the watchdog timer function, otherwise the NMI
detect a hard lockup condition. watchdog — if enabled — can detect a hard lockup condition.
stack_erasing stack_erasing