From: Matthew Dobson <colpatch@us.ibm.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org, akpm@zip.com.au, mingo@redhat.com,
mochel@osdl.org
Subject: Re: [PATCH] Hotplug CPUs for i386 2.5.44
Date: Tue, 29 Oct 2002 11:34:00 -0800 [thread overview]
Message-ID: <3DBEE2A8.6020404@us.ibm.com> (raw)
In-Reply-To: 20021028080437.DE7112C0E3@lists.samba.org
Rusty Russell wrote:
> Doesn't apply to -mm5 because someone did wierd things with the CPU
> placement in driverfs, which clashes with this patch which moves it to
> kernel/cpu.c...
>
> Usage:
> 1) Apply patch, and boot resulting kernel.
> 2) echo 0 > /devices/root/sys/cpu0/online
> 3) echo 1 > /devices/root/sys/cpu0/online
<grins sheepishly>
Errr.. you may want to use
/devices/class/cpu/devices/[0..num_online_cpus()]. There are symlinks
here for every registered CPU device, no matter how some NUMA wacko
rearranges the root/sys directory topology. ;)
Cheers!
-Matt
> The CPU actually spins with interrupts off, doing cpu_relax() and
> polling a variable. It's basically useful for testing the unplug
> infrastructure and benchmarking.
>
> http://www.kernel.org/pub/linux/kernel/people/rusty/patches/hotcpu-x86-28-10-2002.2.5.44.diff.gz
>
> Cheers!
> Rusty.
> --
> Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2002-10-29 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 8:04 [PATCH] Hotplug CPUs for i386 2.5.44 Rusty Russell
2002-01-15 19:34 ` Pavel Machek
2002-10-29 19:34 ` Matthew Dobson [this message]
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=3DBEE2A8.6020404@us.ibm.com \
--to=colpatch@us.ibm.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mochel@osdl.org \
--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