linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wang Qing <wangqing@vivo.com>
To: Jonathan Corbet <corbet@lwn.net>, Wang Qing <wangqing@vivo.com>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Joe Perches <joe@perches.com>, Stephen Kitt <steve@sk2.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Kees Cook <keescook@chromium.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	"Guilherme G. Piccoli" <gpiccoli@canonical.com>,
	Qais Yousef <qais.yousef@arm.com>, Petr Mladek <pmladek@suse.com>,
	Santosh Sivaraj <santosh@fossix.org>,
	Vlastimil Babka <vbabka@suse.cz>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH V2,RESEND 4/4] doc: watchdog: Modify the doc related to "watchdog/%u"
Date: Thu, 29 Apr 2021 17:04:28 +0800	[thread overview]
Message-ID: <1619687073-24686-5-git-send-email-wangqing@vivo.com> (raw)
In-Reply-To: <1619687073-24686-2-git-send-email-wangqing@vivo.com>

"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


  parent reply	other threads:[~2021-04-29  9:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29  9:04 [PATCH V2,RESEND 1/4] kernel: watchdog: Modify the explanation related to watchdog thread Wang Qing
2021-04-29  9:04 ` [PATCH V2,RESEND 2/4] doc: watchdog: Delete the explanation about "watchdog/%u" Wang Qing
2021-04-29  9:04 ` [PATCH V2,RESEND 3/4] doc: watchdog: Modify the explanation related to watchdog thread Wang Qing
2021-04-29  9:04 ` Wang Qing [this message]
2021-04-29  9:29 ` [PATCH V2,RESEND 1/4] kernel: " Petr Mladek
2021-05-09 23:29   ` Andrew Morton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1619687073-24686-5-git-send-email-wangqing@vivo.com \
    --to=wangqing@vivo.com \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=gpiccoli@canonical.com \
    --cc=joe@perches.com \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=pmladek@suse.com \
    --cc=qais.yousef@arm.com \
    --cc=rdunlap@infradead.org \
    --cc=santosh@fossix.org \
    --cc=steve@sk2.org \
    --cc=vbabka@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).