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,
Mathieu Chouquet-Stringer <me@mathieu.digital>
Subject: [PATCH V2,RESEND 2/4] doc: watchdog: Delete the explanation about "watchdog/%u".
Date: Thu, 29 Apr 2021 17:04:26 +0800 [thread overview]
Message-ID: <1619687073-24686-3-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, so delete the explanation about "watchdog/%u".
Signed-off-by: Wang Qing <wangqing@vivo.com>
---
.../admin-guide/kernel-per-CPU-kthreads.rst | 20 --------------------
1 file changed, 20 deletions(-)
diff --git a/Documentation/admin-guide/kernel-per-CPU-kthreads.rst b/Documentation/admin-guide/kernel-per-CPU-kthreads.rst
index 531f689..5e51ee5
--- a/Documentation/admin-guide/kernel-per-CPU-kthreads.rst
+++ b/Documentation/admin-guide/kernel-per-CPU-kthreads.rst
@@ -332,23 +332,3 @@ To reduce its OS jitter, do at least one of the following:
kthreads from being created in the first place. However, please
note that this will not eliminate OS jitter, but will instead
shift it to RCU_SOFTIRQ.
-
-Name:
- watchdog/%u
-
-Purpose:
- Detect software lockups on each CPU.
-
-To reduce its OS jitter, do at least one of the following:
-
-1. Build with CONFIG_LOCKUP_DETECTOR=n, which will prevent these
- kthreads from being created in the first place.
-2. Boot with "nosoftlockup=0", which will also prevent these kthreads
- from being created. Other related watchdog and softlockup boot
- parameters may be found in Documentation/admin-guide/kernel-parameters.rst
- and Documentation/watchdog/watchdog-parameters.rst.
-3. Echo a zero to /proc/sys/kernel/watchdog to disable the
- watchdog timer.
-4. Echo a large number of /proc/sys/kernel/watchdog_thresh in
- order to reduce the frequency of OS jitter due to the watchdog
- timer down to a level that is acceptable for your workload.
--
2.7.4
next prev 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 ` Wang Qing [this message]
2021-04-29 9:04 ` [PATCH V2,RESEND 3/4] doc: " Wang Qing
2021-04-29 9:04 ` [PATCH V2,RESEND 4/4] doc: watchdog: Modify the doc related to "watchdog/%u" Wang Qing
2021-04-29 9:29 ` [PATCH V2,RESEND 1/4] kernel: watchdog: Modify the explanation related to watchdog thread 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-3-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=me@mathieu.digital \
--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).