From: Paul Mackerras <paulus@samba.org>
To: Nathan Fontenot <nfont@austin.ibm.com>
Cc: linuxppc-dev@ozlabs.org, gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] sysfs cpu probe/release files
Date: Thu, 26 Nov 2009 13:59:32 +1100 [thread overview]
Message-ID: <19213.61204.591278.856459@drongo.ozlabs.ibm.com> (raw)
In-Reply-To: <4B0CD8D5.8050803@austin.ibm.com>
Nathan Fontenot writes:
> In order to support kernel DLPAR of CPU resources we need to provide an
> interface to add (probe) and remove (release) the resource from the system.
> This patch Creates new generic probe and release sysfs files to facilitate
> cpu probe/release. The probe/release interface provides for allowing each
> arch to supply their own routines for implementing the backend of adding
> and removing cpus to/from the system.
>
> This also creates the powerpc specific stubs to handle the arch callouts
> from writes to the sysfs files.
>
> The creation and use of these files is regulated by the
> CONFIG_ARCH_CPU_PROBE_RELEASE option so that only architectures that need the
> capability will have the files created.
>
> Signed-off-by: Nathan Fontenot <nfont@austin.ibm.com>
Acked-by: Paul Mackerras <paulus@samba.org>
next prev parent reply other threads:[~2009-11-26 2:59 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 [this message]
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
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=19213.61204.591278.856459@drongo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=nfont@austin.ibm.com \
/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).