mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zqiang <qiang.zhang1211@gmail.com>
To: Petr Mladek <pmladek@suse.com>
Cc: akpm@linux-foundation.org, frederic@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] watchdog: ignore nohz_full cores in new cpumask
Date: Tue, 16 Nov 2021 14:04:57 +0800	[thread overview]
Message-ID: <a8426729-6fd8-4855-d934-552d80f74561@gmail.com> (raw)
In-Reply-To: <YZJ9ZNusQR/3nh/9@alley>


On 2021/11/15 下午11:31, Petr Mladek wrote:
> On Fri 2021-11-12 13:14:34, Zqiang wrote:
>> If the nohz_full is enabled, when update watchdog_mask, the
>> nohz_full cores should be ignored.
>>
>> Signed-off-by: Zqiang <qiang.zhang1211@gmail.com>
>> ---
>>   kernel/watchdog.c | 4 +++-
>>   1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/kernel/watchdog.c b/kernel/watchdog.c
>> index ad912511a0c0..3ef11a94783c 100644
>> --- a/kernel/watchdog.c
>> +++ b/kernel/watchdog.c
>> @@ -628,7 +628,9 @@ void lockup_detector_soft_poweroff(void)
>>   static void proc_watchdog_update(void)
>>   {
>>   	/* Remove impossible cpus to keep sysctl output clean. */
>> -	cpumask_and(&watchdog_cpumask, &watchdog_cpumask, cpu_possible_mask);
>> +	cpumask_and(&watchdog_cpumask, &watchdog_cpumask,
>> housekeeping_cpumask(HK_FLAG_TIMER));
> I am not familiar with nozh_full code but this looks fine.
>
>
>> +	if (cpumask_empty(&watchdog_cpumask))
>> +		return;
> But this looks looks wrong. Is there any reason for this?
>
> We need to stop the watchdog when it was running before.
>
> I mean that lockup_detector_reconfigure() must be called anytime
> when the mask has changed even when it became empty.

Thanks Petr

I will resend patch v2.

>
>
>>   	lockup_detector_reconfigure();
>>   }
> Best Regards,
> Petr

      reply	other threads:[~2021-11-16  6:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12  5:14 Zqiang
2021-11-15 15:31 ` Petr Mladek
2021-11-16  6:04   ` 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=a8426729-6fd8-4855-d934-552d80f74561@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®