From: Nathan Fontenot <nfont@austin.ibm.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linuxppc-dev@ozlabs.org, gregkh@suse.de,
paul Mackerras <paulus@samba.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Kernel handling of Dynamic Logical Partitioning
Date: Mon, 30 Nov 2009 14:48:20 -0600 [thread overview]
Message-ID: <4B142F94.7010602@austin.ibm.com> (raw)
In-Reply-To: <m13a3ztwtw.fsf@fess.ebiederm.org>
Eric W. Biederman wrote:
> Nathan Fontenot <nfont@austin.ibm.com> writes:
>
>> version 2 of the patch set with updates from comments.
>>
>> The Dynamic Logical Partitioning (DLPAR) capabilities of the powerpc pseries
>> platform allows for the addition and removal of resources (i.e. cpus,
>> memory, pci devices) from a partition. The removal of a resource involves
>> removing the resource's node from the device tree and then returning the
>> resource to firmware via the rtas set-indicator call. To add a resource, it
>> is first obtained from firmware via the rtas set-indicator call and then a
>> new device tree node is created using the ibm,configure-coinnector rtas call
>> and added to the device tree.
>>
>> The following set of patches implements the needed infrastructure to have the
>> kernel handle the DLPAR addition and removal of cpus (other DLPAR'able items to
>> follow in future patches). The framework for this is to create a set of
>> probe/release sysfs files that will facilitate arch-specific call-outs to handle
>> addition and removal of cpus to the system.
>
> How does this differ from /sys/devices/system/cpu/cpuX/online ?
>
> From the descriptions it appears that we already have what you are trying to
> add and you just need to tie it into DLPAR on ppc.
>
The DLPAR and hotplug operations need to be kept separate for ppc. One big reason
for this is that DLPAR operations on ppc are driven from the Hardware Management
Console (HMC). It is (almost always) not possible to DLPAR add a resource (i.e.
cpu, memory,pcie device) from the OS. There are HMC <=> firmware interactions
that must occur to make the resource available to the partition.
Second is that there are times when one would want to hotplug add/remove
a cpu but not dlpar add/remove it.
When a resource is DLPAR removed, the OS has no knowledge that the resource exists.
Likewise, this allows the addition of resources from the HMC after the system is booted.
This is a feature of ppc partitions that allows for the dynamic movement of resources
between partitions.
-Nathan Fontenot
prev parent reply other threads:[~2009-11-30 20:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 7:04 [PATCH v2 0/3] Kernel handling of Dynamic Logical Partitioning Nathan Fontenot
2009-11-25 7:10 ` [PATCH v2 1/3] Kernel DLPAR Infrastructure Nathan Fontenot
2009-11-26 2:59 ` Paul Mackerras
2009-11-25 7:12 ` [PATCH v2 2/3] sysfs cpu probe/release files Nathan Fontenot
2009-11-25 13:01 ` Greg KH
2009-11-26 2:59 ` Paul Mackerras
2009-11-26 3:23 ` [PATCH v3 " Nathan Fontenot
2009-11-25 7:13 ` [PATCH v2 3/3]CPU DLPAR handling Nathan Fontenot
2009-11-26 2:59 ` Paul Mackerras
2009-11-27 22:41 ` [PATCH v2 0/3] Kernel handling of Dynamic Logical Partitioning Eric W. Biederman
2009-11-30 20:48 ` Nathan Fontenot [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=4B142F94.7010602@austin.ibm.com \
--to=nfont@austin.ibm.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).