public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@kernel.org>,
	linux-kernel@vger.kernel.org, jschoenh@amazon.de,
	oleg@redhat.com
Subject: Re: [PATCH] sched: Allow per-cpu kernel threads to run on online && !active
Date: Thu, 3 Mar 2016 12:55:53 +0100	[thread overview]
Message-ID: <20160303115553.GN6344@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.11.1603031241231.3597@nanos>

On Thu, Mar 03, 2016 at 12:43:53PM +0100, Thomas Gleixner wrote:

> Subject: cpu/hotplug: Handle cpu active as last state
> From: Thomas Gleixner <tglx@linutronix.de>
> Date: Thu, 03 Mar 2016 12:33:37 +0100
> 
> We want to make sure that everything is initialized before we allow scheduling
> of arbitrary work on a upcoming CPU and we don't want to have no more random
> work on it when we shut it down.
> 
> Now that the scheduler handles this nicely via the cpu_active_mask we can put
> set_cpu_active() as last action when a cpu is brought up and as first action
> when it goes down.
> 
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Cc: Peter Zijlstra <peterz@infradead.org>

Nice!

Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>

> ---
>  include/linux/cpuhotplug.h |    1 +
>  kernel/cpu.c               |   19 +++++++++++++++++--
>  kernel/sched/core.c        |   18 ------------------
>  3 files changed, 18 insertions(+), 20 deletions(-)
> 
> +++ b/kernel/sched/core.c
> @@ -5726,23 +5726,6 @@ static int sched_cpu_active(struct notif
>  	case CPU_STARTING:
>  		set_cpu_rq_start_time();

If we stick that in notify_starting() we can kill all of this.

>  		return NOTIFY_OK;
> -
> -	case CPU_DOWN_FAILED:
> -		set_cpu_active(cpu, true);
> -		return NOTIFY_OK;
> -
> -	default:
> -		return NOTIFY_DONE;
> -	}
> -}
> -
> -static int sched_cpu_inactive(struct notifier_block *nfb,
> -					unsigned long action, void *hcpu)
> -{
> -	switch (action & ~CPU_TASKS_FROZEN) {
> -	case CPU_DOWN_PREPARE:
> -		set_cpu_active((long)hcpu, false);
> -		return NOTIFY_OK;
>  	default:
>  		return NOTIFY_DONE;
>  	}
> @@ -5761,7 +5744,6 @@ static int __init migration_init(void)
>  
>  	/* Register cpu active notifiers */
>  	cpu_notifier(sched_cpu_active, CPU_PRI_SCHED_ACTIVE);
> -	cpu_notifier(sched_cpu_inactive, CPU_PRI_SCHED_INACTIVE);
>  
>  	return 0;
>  }

  reply	other threads:[~2016-03-03 11:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01 15:23 [PATCH] sched: Allow per-cpu kernel threads to run on online && !active Peter Zijlstra
2016-03-03 11:43 ` Thomas Gleixner
2016-03-03 11:55   ` Peter Zijlstra [this message]
2016-03-03 11:58     ` Thomas Gleixner
2016-03-03 17:45       ` Thomas Gleixner
2016-05-05 11:21 ` [tip:smp/hotplug] " tip-bot for Peter Zijlstra (Intel)
2016-05-06 13:03 ` tip-bot for Peter Zijlstra (Intel)

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=20160303115553.GN6344@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=jschoenh@amazon.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.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