mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zqiang <qiang.zhang1211@gmail.com>
To: frederic@kernel.org, pmladek@suse.com
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] watchdog: Add warning message when the newcpumask contains nohz_full cores
Date: Mon, 22 Nov 2021 19:13:20 +0800	[thread overview]
Message-ID: <c4adfc53-9471-6cb9-c263-5f462469db1a@gmail.com> (raw)
In-Reply-To: <20211118031046.32632-1-qiang.zhang1211@gmail.com>


On 2021/11/18 上午11:10, Zqiang wrote:
> The watchdog default is disabled on nohz_full cores, however when
> override the cpumask, if new cpumask contains nohz_full cores,
> add warning message.
>
> Signed-off-by: Zqiang <qiang.zhang1211@gmail.com>
> ---
>   v1->v2:
>   if watchdog_cpumask became empty, set housekeeping_cpumask.
>   v2->v3:
>   only print a warning when a nohz_full CPU is included in new cpumask.
>
>   kernel/watchdog.c | 1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/kernel/watchdog.c b/kernel/watchdog.c
> index ad912511a0c0..37a978d8ff06 100644
> --- a/kernel/watchdog.c
> +++ b/kernel/watchdog.c
> @@ -629,6 +629,7 @@ static void proc_watchdog_update(void)
>   {
>   	/* Remove impossible cpus to keep sysctl output clean. */
>   	cpumask_and(&watchdog_cpumask, &watchdog_cpumask, cpu_possible_mask);
> +	WARN_ONCE(!cpumask_subset(&watchdog_cpumask, housekeeping_cpumask(HK_FLAG_TIMER)), "Enabling watchdog on nohz_full cores\n");
>   	lockup_detector_reconfigure();
>   }
>   

Hello Frederic

Can you give some suggestions?

Thanks

Zqiang


      reply	other threads:[~2021-11-22 11:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18  3:10 Zqiang
2021-11-22 11:13 ` Zqiang [this message]

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=c4adfc53-9471-6cb9-c263-5f462469db1a@gmail.com \
    --to=qiang.zhang1211@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    /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

all inboxes | Powered by JetHome®