Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-15.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER, INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C4D92C07E9B for ; Tue, 6 Jul 2021 19:08:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id AE15561C87 for ; Tue, 6 Jul 2021 19:08:47 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231740AbhGFTL0 (ORCPT ); Tue, 6 Jul 2021 15:11:26 -0400 Received: from mail.kernel.org ([198.145.29.99]:46146 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231730AbhGFTLZ (ORCPT ); Tue, 6 Jul 2021 15:11:25 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id A617261C6F; Tue, 6 Jul 2021 19:08:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1625598527; bh=5lu/NoPZNVmOdaKPHSzP62WNXqB6PRTCf4MXG3pjvc0=; h=Date:From:To:Subject:From; b=GUc2i4USGswYgVw7Cx+mgGK76L3qqQfEnI1cxX4SR6uyISoPU8/vozYdSU8YDweIx +6mE7L12EhbgytJe/9I18Nk9RC2DUkpkjz8fb261LFClq9y2VXSZleAzCNkDShxbnV Gr4eT/jarvDBkv+g+mPEF+yu9H761DGab8Hil27Q= Date: Tue, 06 Jul 2021 12:08:46 -0700 From: akpm@linux-foundation.org To: corbet@lwn.net, gpiccoli@canonical.com, joe@perches.com, keescook@chromium.org, mchehab+huawei@kernel.org, mm-commits@vger.kernel.org, pmladek@suse.com, qais.yousef@arm.com, rdunlap@infradead.org, santosh@fossix.org, steve@sk2.org, vbabka@suse.cz, wangqing@vivo.com Subject: [merged] doc-watchdog-modify-the-explanation-related-to-watchdog-thread.patch removed from -mm tree Message-ID: <20210706190846.xt-4tM2Wj%akpm@linux-foundation.org> User-Agent: s-nail v14.8.16 Precedence: bulk Reply-To: linux-kernel@vger.kernel.org List-ID: X-Mailing-List: mm-commits@vger.kernel.org The patch titled Subject: doc: watchdog: modify the explanation related to watchdog thread has been removed from the -mm tree. Its filename was doc-watchdog-modify-the-explanation-related-to-watchdog-thread.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: Wang Qing Subject: 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/1619687073-24686-4-git-send-email-wangqing@vivo.com Signed-off-by: Wang Qing Reviewed-by: Petr Mladek Cc: "Guilherme G. Piccoli" Cc: Joe Perches Cc: Jonathan Corbet Cc: Kees Cook Cc: Mauro Carvalho Chehab Cc: Qais Yousef Cc: Randy Dunlap Cc: Santosh Sivaraj Cc: Stephen Kitt Cc: Vlastimil Babka Signed-off-by: Andrew Morton --- Documentation/admin-guide/lockup-watchdogs.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) --- a/Documentation/admin-guide/lockup-watchdogs.rst~doc-watchdog-modify-the-explanation-related-to-watchdog-thread +++ a/Documentation/admin-guide/lockup-watchdogs.rst @@ -39,7 +39,7 @@ in principle, they should work in any ar 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 d 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) _ Patches currently in -mm which might be from wangqing@vivo.com are