From: Pavel Machek <pavel@suse.cz>
To: Rusty Russell <rusty@linuxcare.com.au>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Hot swap CPU support for 2.4.1
Date: Sun, 11 Feb 2001 00:29:55 +0100 [thread overview]
Message-ID: <20010211002955.I7877@bug.ucw.cz> (raw)
In-Reply-To: <E14PcpU-0004U1-00@halfway>
In-Reply-To: <E14PcpU-0004U1-00@halfway>; from Rusty Russell on Mon, Feb 05, 2001 at 03:00:40PM +1100
Hi!
> I did the infrastructure, Anton did the bugfinding and PPC support,
> aka. the hard stuff. Other architectures need to implement
> __cpu_disable, __cpu_die and __cpu_up for them to work. Volunteers
> appreciated.
>
> This patch allows you to down & up CPUs as follows:
> # echo 0 > /proc/sys/cpu/0/online
> # echo 1 > /proc/sys/cpu/0/online
>
> The relatively trivial patch works as follows:
>
> 1) Implements synchronize_kernel() (thanks Andi Kleen for forwarding
> Paul McKenney's quiescent-state ideas) which waits for a schedule
> on all CPUs.
> 2) All CPU numbers are now physical: removes cpu_number_map,
> cpu_logical_map and smp_num_cpus.
> 3) Adds cpu_online(cpu) and cpu_num_online() macros.
> 4) Adds cpu_down() and cpu_up() calls, which call arch-specific
> __cpu_disable(cpu), __cpu_die(cpu) and __cpu_up(cpu).
> 5) Fixes schedule() to check allowed_cpus even if rescheduling same
> task.
This is not quite right:
@@ -1643,7 +1643,7 @@
printk(KERN_NOTICE "apm: disabled on user
request.\n");
return -ENODEV;
}
- if ((smp_num_cpus > 1) && !power_off) {
+ if ((num_online_cpus() > 1) && !power_off) {
printk(KERN_NOTICE "apm: disabled - APM is not SMP
safe.\n");
return -ENODEV;
}
@@ -1697,7 +1697,7 @@
kernel_thread(apm, NULL, CLONE_FS | CLONE_FILES |
CLONE_SIGHAND | SIGCHLD);
- if (smp_num_cpus > 1) {
+ if (num_online_cpus() > 1) {
printk(KERN_NOTICE
"apm: disabled - APM is not SMP safe (power off
active).\n");
return 0;
I do not think it is safe to call APM when there is just CPU #5
running. smp_num_cpus in this context means "if we ever had more than
boot cpu".
Pavel
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-11 10:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-05 4:00 [PATCH] Hot swap CPU support for 2.4.1 Rusty Russell
2001-02-05 5:50 ` Lars Marowsky-Bree
2001-02-05 6:06 ` Anton Blanchard
2001-02-05 21:19 ` [PATCH] Hot swap CPU support for 2.4.1@ lists
2001-02-06 14:17 ` Anton Blanchard
2001-02-10 23:29 ` Pavel Machek [this message]
2001-02-11 23:05 ` [PATCH] Hot swap CPU support for 2.4.1 Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2001-02-05 4:51 Frank Davis
2001-02-05 6:54 ` Rusty Russell
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=20010211002955.I7877@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@linuxcare.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