mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Siddha@cborntra, Suresh B <suresh.b.siddha@intel.com>
Subject: [PATCH/RFC] NOHZ: fix nohz on cpu unplug
Date: Mon, 2 Feb 2009 10:58:45 +0100	[thread overview]
Message-ID: <200902021058.45230.borntraeger@de.ibm.com> (raw)
In-Reply-To: <200901301729.30284.borntraeger@de.ibm.com>

This is a reminder mail. I still dont know if my fix is correct, although
it seems to work..
I also CCed: Siddha, Suresh B <suresh.b.siddha@intel.com>

> Ingo, Thomas,
>
> After using cpu unplug I have seen one cpu with enabled ticks on s390,
> even on a idle systems. It turned out that nohz.cpu_mask is not
> updated on cpu unplug.
> In select_nohz_load_balancer we check if the system is completely
> idle to turn of load balancing. We compare the weights of
> cpu_online_map with nohz.cpu_mask.
> Since cpu_online_map is updated on cpu unplug, but nohz.cpu_mask is
> not, the check fails and the scheduler believes that we need an
> "idle load balancer" even on a fully idle system. Since the ilb
> cpu does not deactivate the timer tick this "breaks" NOHZ.
>
> One possible fix is to only add the cpu to the nohz.cpu_mask,
> if the cpu is active.
>
> The alternative is to add nohz.cpu_mask in the cpu hotplug path.
>
> This patch seems to work on s390 (Shortly tested with kvm guests
> with cpu hotplug and kvm_stat on the host), but I want to hear your
> opinion.
>
> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> ---
>  kernel/sched.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: kvm/kernel/sched.c
> ===================================================================
> --- kvm.orig/kernel/sched.c
> +++ kvm/kernel/sched.c
> @@ -3880,7 +3880,8 @@ int select_nohz_load_balancer(int stop_t
>  	int cpu = smp_processor_id();
>
>  	if (stop_tick) {
> -		cpumask_set_cpu(cpu, nohz.cpu_mask);
> +		if (cpu_active(cpu))
> +			cpumask_set_cpu(cpu, nohz.cpu_mask);
>  		cpu_rq(cpu)->in_nohz_recently = 1;
>
>  		/*



  reply	other threads:[~2009-02-02  9:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30 16:29 [RFC] " Christian Borntraeger
2009-02-02  9:58 ` Christian Borntraeger [this message]
2009-02-02 12:23   ` [PATCH v2] " Christian Borntraeger
2009-02-02 23:57     ` Suresh Siddha
2009-02-03  8:48       ` Christian Borntraeger
2009-02-03 12:28         ` Ingo Molnar
2009-02-04  6:19           ` Christian Borntraeger
2009-02-04 19:59             ` Suresh Siddha
2009-02-04 21:32               ` Ingo Molnar
2009-02-05 19:54                 ` Mark Lord
2009-02-06  2:33                   ` Suresh Siddha
2009-02-06 14:52                     ` Mark Lord

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=200902021058.45230.borntraeger@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=Siddha@cborntra \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=schwidefsky@de.ibm.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    /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®