From: Ashok Raj <ashok.raj@intel.com>
To: "Protasevich, Natalie" <Natalie.Protasevich@UNISYS.com>
Cc: Ashok Raj <ashok.raj@intel.com>,
shaohua.li@intel.com, zwane@arm.linux.org.uk, 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, 1 Sep 2005 14:26:59 -0700 [thread overview]
Message-ID: <20050901142659.A29600@unix-os.sc.intel.com> (raw)
In-Reply-To: <19D0D50E9B1D0A40A9F0323DBFA04ACCE04D14@USRV-EXCH4.na.uis.unisys.com>; from Natalie.Protasevich@UNISYS.com on Thu, Sep 01, 2005 at 04:09:09PM -0500
On Thu, Sep 01, 2005 at 04:09:09PM -0500, Protasevich, Natalie 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
> >
> > This sounds like a cluge to me. The correct implementation
> > would be you would need some sysmgmt deamon or something that
> > works with the kernel to notify of new cpus and populate
> > apicid and grow cpu_present_map. Making an assumption that
> > disabled APICID are valid for ES7000 sake is not a safe assumption.
>
> Yes, this is a kludge, I realize that. The AML code was not there so far
> (it will be in the next one). I have a point here though that if the
> processor is there, but is unusable (what "disabled" means as the ACPI
> spec says), meaning bad maybe, then with physical hot plug it can
> certainly be made usable and I think it should be taken into
> consideration (and into configuration). It should be counted as possible
> at least, with hot plug, because it represent existing socket.
I think marking it as present, and considering in cpu_possible_map is perfectly
ok. But we would need more glue logic, that is if firmware marked it as
disabled, then one would expect you then run _STA and find that the CPU
is now present and functional as reported by _STA, then the CPU is onlinable.
So if _STA can work favorably in your case you can use it to override the
disabled setting at boot time which would be prefectly fine.
>
--
Cheers,
Ashok Raj
- Open Source Technology Center
next prev parent reply other threads:[~2005-09-01 21:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 21:09 [patch 1/1] Hot plug CPU to support physical add of new processors (i386) Protasevich, Natalie
2005-09-01 21:26 ` Ashok Raj [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-20 23:57 Natalie.Protasevich
2005-09-01 22:56 Protasevich, Natalie
2005-09-01 13:43 Protasevich, Natalie
2005-08-31 12:13 Natalie.Protasevich
2005-09-01 8:00 ` Shaohua Li
2005-09-01 8:45 ` Andi Kleen
2005-09-01 17:53 ` Ashok Raj
2005-09-01 17:36 ` Ashok Raj
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=20050901142659.A29600@unix-os.sc.intel.com \
--to=ashok.raj@intel.com \
--cc=Natalie.Protasevich@UNISYS.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=hotplug_sig@lists.osdl.org \
--cc=lhcs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--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