[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1617247900-23813-5-git-send-email-wangqing@vivo.com>
Date: Thu, 1 Apr 2021 11:31:34 +0800
From: Wang Qing <wangqing@...o.com>
To: Jonathan Corbet <corbet@....net>, Joe Perches <joe@...ches.com>,
Wang Qing <wangqing@...o.com>,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
Stephen Kitt <steve@....org>,
Andrew Morton <akpm@...ux-foundation.org>,
Kees Cook <keescook@...omium.org>,
Randy Dunlap <rdunlap@...radead.org>,
"Guilherme G. Piccoli" <gpiccoli@...onical.com>,
Eric Biggers <ebiggers@...gle.com>,
Qais Yousef <qais.yousef@....com>,
Petr Mladek <pmladek@...e.com>,
Vlastimil Babka <vbabka@...e.cz>,
Santosh Sivaraj <santosh@...six.org>,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
Alexey Budankov <alexey.budankov@...ux.intel.com>,
Andrey Ignatov <rdna@...com>
Cc: gregkh@...uxfoundation.org
Subject: [PATCH V2 4/4] 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.
---
Documentation/admin-guide/sysctl/kernel.rst | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
index 1d56a6b..32b0791
--- a/Documentation/admin-guide/sysctl/kernel.rst
+++ b/Documentation/admin-guide/sysctl/kernel.rst
@@ -1282,11 +1282,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
-without rescheduling voluntarily, and thus prevent the 'watchdog/N' threads
-from running. The mechanism depends on the CPUs ability to respond to timer
-interrupts which are needed for the 'watchdog/N' threads to be woken up by
-the watchdog timer function, otherwise the NMI watchdog — if enabled — can
-detect a hard lockup condition.
+without rescheduling voluntarily, and thus prevent the 'migration/N' threads
+from running, causing the watchdog work fail to execute. The mechanism depends
+on the CPUs ability to respond to timer interrupts which are needed for the
+watchdog work to be queued by the watchdog timer function, otherwise the NMI
+watchdog — if enabled — can detect a hard lockup condition.
stack_erasing
--
2.7.4
Powered by blists - more mailing lists