From: Shaohua Li <shaohua.li@intel.com>
To: Natalie.Protasevich@unisys.com
Cc: zwane@arm.linux.org.uk, "Raj, Ashok" <ashok.raj@intel.com>,
akpm@osdl.org, ak@suse.de, lhcs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, hotplug_sig@lists.osdl.org
Subject: Re: [patch 1/1] Hot plug CPU to support physical add of new processors (i386)
Date: Thu, 01 Sep 2005 16:00:58 +0800 [thread overview]
Message-ID: <1125561658.4005.6.camel@linux-hp.sh.intel.com> (raw)
In-Reply-To: <20050831121311.5FC7C57D99@linux.site>
Hi,
On Wed, 2005-08-31 at 20:13 +0800, Natalie.Protasevich@unisys.com wrote:
> Current IA32 CPU hotplug code doesn't allow bringing up processors
> that were not present in the boot configuration.
> To make existing hot plug facility more practical for physical hot
> plug, possible processors should be encountered
> during boot for potentual hot add/replace/remove. On ES7000, ACPI
> marks all the sockets that are empty or not assigned
> to the partitionas as "disabled". The patch allows arrays/masks with
> APIC info for disabled processors to be
> initialized. Then the OS can bring up a processor that was inserted in
> the socked and brought into configuration
> during runtime.
> To test the code, one can boot the system with maxcpu=1 and then bring
> the rest of the processors up, which was not
> possible so far (only maxcpus number of nodes were created).
> The patch also makes proc entry for interrupts dynamically change to
> only show current onlined processors.
Could we clean up the cpu_present_map a bit, like IA64 does? Eg, if a
new CPU is inserted, we allocated cpu id for it and set cpu_present_map.
Current alloc_cpu_id is just a workaround for suspend/resume use, but
isn't ok for physical cpu hotplug to me.
Thanks,
Shaohua
next prev parent reply other threads:[~2005-09-01 7:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 12:13 [patch 1/1] Hot plug CPU to support physical add of new processors (i386) Natalie.Protasevich
2005-09-01 8:00 ` Shaohua Li [this message]
2005-09-01 8:45 ` Andi Kleen
2005-09-01 17:53 ` Ashok Raj
2005-09-01 15:30 ` [Hotplug_sig] " Nathan Lynch
2005-09-01 17:36 ` Ashok Raj
-- strict thread matches above, loose matches on Subject: below --
2005-09-01 13:43 Protasevich, Natalie
2005-09-01 21:09 Protasevich, Natalie
2005-09-01 21:26 ` Ashok Raj
2005-09-01 22:56 Protasevich, Natalie
2005-09-20 23:57 Natalie.Protasevich
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=1125561658.4005.6.camel@linux-hp.sh.intel.com \
--to=shaohua.li@intel.com \
--cc=Natalie.Protasevich@unisys.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=hotplug_sig@lists.osdl.org \
--cc=lhcs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@arm.linux.org.uk \
/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