public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@linuxcare.com.au>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] Hot swap CPU support for 2.4.1
Date: Mon, 05 Feb 2001 15:00:40 +1100	[thread overview]
Message-ID: <E14PcpU-0004U1-00@halfway> (raw)

[-- Attachment #1: Type: text/plain, Size: 982 bytes --]

Hi all,

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.

Since it's 60k long, mime attached bzip2.

Go hack!
Rusty Russell & Anton Blanchard
--

[-- Attachment #2: hotswap CPU patch --]
[-- Type: application/octet-stream, Size: 13894 bytes --]

             reply	other threads:[~2001-02-05  4:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-05  4:00 Rusty Russell [this message]
2001-02-05  5:50 ` [PATCH] Hot swap CPU support for 2.4.1 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 ` [PATCH] Hot swap CPU support for 2.4.1 Pavel Machek
2001-02-11 23:05   ` 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=E14PcpU-0004U1-00@halfway \
    --to=rusty@linuxcare.com.au \
    --cc=linux-kernel@vger.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