mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Robin Holt <holt@sgi.com>
Cc: Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
	"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
	Russ Anderson <rja@sgi.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [PATCH -v6 2/5] Migrate shutdown/reboot to boot cpu.
Date: Wed, 24 Apr 2013 15:17:49 -0700	[thread overview]
Message-ID: <20130424151749.30b0680dc9392b110537bcd5@linux-foundation.org> (raw)
In-Reply-To: <1366802333-8890-3-git-send-email-holt@sgi.com>

On Wed, 24 Apr 2013 06:18:50 -0500 Robin Holt <holt@sgi.com> wrote:

> We recently noticed that reboot of a 1024 cpu machine takes approx 16
> minutes of just stopping the cpus.  The slowdown was tracked to commit
> f96972f.
> 
> The current implementation does all the work of hot removing the cpus
> before halting the system.  We are switching to just migrating to the
> boot cpu and then continuing with shutdown/reboot.
> 
> This also has the effect of not breaking x86's command line parameter for
> specifying the reboot cpu.  Note, this code was shamelessly copied from
> arch/x86/kernel/reboot.c with bits removed pertaining to the reboot_cpu
> command line parameter.
> 
> @@ -357,6 +357,24 @@ int unregister_reboot_notifier(struct notifier_block *nb)
>  }
>  EXPORT_SYMBOL(unregister_reboot_notifier);
>  
> +static void migrate_to_reboot_cpu(void)
> +{
> +	/* The boot cpu is always logical cpu 0 */
> +	int reboot_cpu_id = 0;
> +
> +	cpu_hotplug_disable();
> +
> +	/* Make certain the cpu I'm about to reboot on is online */
> +	if (!cpu_online(reboot_cpu_id))
> +		reboot_cpu_id = cpumask_first(cpu_online_mask);
> +
> +	/* Prevent races with other tasks migrating this task */
> +	current->flags |= PF_THREAD_BOUND;

PF_THREAD_BOUND was removed/replaced in linux-next's a9ab775bc
("workqueue: directly restore CPU affinity of workers from CPU_ONLINE")



  reply	other threads:[~2013-04-24 22:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24 11:18 [PATCH -v6 0/5] Shutdown from reboot_cpuid without stopping other cpus Robin Holt
2013-04-24 11:18 ` [PATCH -v6 1/5] CPU hotplug: Provide a generic helper to disable/enable CPU hotplug Robin Holt
2013-04-24 11:18 ` [PATCH -v6 2/5] Migrate shutdown/reboot to boot cpu Robin Holt
2013-04-24 22:17   ` Andrew Morton [this message]
2013-04-24 22:19     ` Andrew Morton
2013-04-25  6:57     ` Ingo Molnar
2013-04-25  7:29       ` Andrew Morton
2013-04-25  7:34         ` Ingo Molnar
2013-04-25 15:36           ` Robin Holt
2013-04-24 11:18 ` [PATCH -v6 3/5] Move shutdown/reboot related functions to kernel/reboot.c Robin Holt
2013-04-24 11:18 ` [PATCH -v6 4/5] checkpatch.pl the new kernel/reboot.c file Robin Holt
2013-04-24 11:18 ` [PATCH -v6 5/5] Move arch/x86 reboot= handling to generic kernel Robin Holt
2013-04-24 22:11   ` Andrew Morton
2013-04-25 21:23 ` [PATCH -v6 0/5] Shutdown from reboot_cpuid without stopping other cpus Robin Holt

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=20130424151749.30b0680dc9392b110537bcd5@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=holt@sgi.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=rja@sgi.com \
    --cc=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=x86@kernel.org \
    /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®