From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
rusty@rustcorp.com.au
Subject: CPU hotplug on i386
Date: Wed, 16 Mar 2005 14:21:52 +0100 [thread overview]
Message-ID: <20050316132151.GA2227@elf.ucw.cz> (raw)
Hi!
I tried to solve long-standing uglyness in swsusp cmp code by calling
cpu hotplug... only to find out that CONFIG_CPU_HOTPLUG is not
available on i386. Is there way to enable CPU_HOTPLUG on i386?
Pavel
--- clean/kernel/power/smp.c 2004-08-15 19:15:06.000000000 +0200
+++ linux/kernel/power/smp.c 2005-03-16 14:16:00.000000000 +0100
@@ -16,70 +16,39 @@
#include <asm/atomic.h>
#include <asm/tlbflush.h>
-static atomic_t cpu_counter, freeze;
-
-
-static void smp_pause(void * data)
-{
- struct saved_context ctxt;
- __save_processor_state(&ctxt);
- printk("Sleeping in:\n");
- dump_stack();
- atomic_inc(&cpu_counter);
- while (atomic_read(&freeze)) {
- /* FIXME: restore takes place at random piece inside this.
- This should probably be written in assembly, and
- preserve general-purpose registers, too
-
- What about stack? We may need to move to new stack here.
-
- This should better be ran with interrupts disabled.
- */
- cpu_relax();
- barrier();
- }
- atomic_dec(&cpu_counter);
- __restore_processor_state(&ctxt);
-}
-
-cpumask_t oldmask;
+cpumask_t frozen_cpus;
void disable_nonboot_cpus(void)
{
- printk("Freezing CPUs (at %d)", smp_processor_id());
- oldmask = current->cpus_allowed;
- set_cpus_allowed(current, cpumask_of_cpu(0));
- current->state = TASK_INTERRUPTIBLE;
- schedule_timeout(HZ);
- printk("...");
- BUG_ON(smp_processor_id() != 0);
-
- /* FIXME: for this to work, all the CPUs must be running
- * "idle" thread (or we deadlock). Is that guaranteed? */
-
- atomic_set(&cpu_counter, 0);
- atomic_set(&freeze, 1);
- smp_call_function(smp_pause, NULL, 0, 0);
- while (atomic_read(&cpu_counter) < (num_online_cpus() - 1)) {
- cpu_relax();
- barrier();
+ int cpu, error;
+ cpus_clear(frozen_cpus);
+ printk("Freezing cpus...\n");
+ for_each_online_cpu(cpu) {
+ if (!cpu)
+ continue;
+ cpu_set(cpu, frozen_cpus);
+ error = cpu_down(cpu);
+ if (!error)
+ continue;
+ printk("Error taking cpu %d down: %d\n", cpu, error);
+ panic("Too many cpus");
}
- printk("ok\n");
+ BUG_ON(smp_processor_id() != 0);
}
void enable_nonboot_cpus(void)
{
- printk("Restarting CPUs");
- atomic_set(&freeze, 0);
- while (atomic_read(&cpu_counter)) {
- cpu_relax();
- barrier();
+ int cpu, error;
+ printk("Thawing cpus...\n");
+ for_each_cpu_mask(cpu, frozen_cpus) {
+ if (!cpu)
+ continue;
+ error = cpu_up(cpu);
+ if (!error)
+ continue;
+ printk("Error taking cpu %d up: %d\n", cpu, error);
+ panic("Not enough cpus");
}
- printk("...");
- set_cpus_allowed(current, oldmask);
- schedule();
- printk("ok\n");
-
}
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next reply other threads:[~2005-03-16 13:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 13:21 Pavel Machek [this message]
2005-03-16 14:40 ` CPU hotplug on i386 Rafael J. Wysocki
2005-03-17 0:40 ` Nigel Cunningham
2005-03-16 17:09 ` Nathan Lynch
2005-03-16 19:20 ` Zwane Mwaikambo
2005-03-16 23:51 ` Rafael J. Wysocki
2005-03-17 0:04 ` Pavel Machek
2005-03-17 0:16 ` Rafael J. Wysocki
2005-03-16 18:49 ` Nathan Lynch
2005-03-16 20:51 ` Pavel Machek
2005-03-18 11:45 ` Pavel Machek
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=20050316132151.GA2227@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=rusty@rustcorp.com.au \
/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