From: Michael Bringmann <mwb@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: [PATCH V8 0/8] powerpc/devtree: Add support for 2 new DRC properties
Date: Tue, 25 Oct 2016 16:32:05 -0500 [thread overview]
Message-ID: <20161025213117.165626.94076.stgit@powerkvm6.aus.stglabs.ibm.com> (raw)
Several properties in the DRC device tree format are replaced by
more compact representations to allow, for example, for the encoding
of vast amounts of memory, and or reduced duplication of information
in related data structures.
"ibm,drc-info": This property, when present, replaces the following
four properties: "ibm,drc-indexes", "ibm,drc-names", "ibm,drc-types"
and "ibm,drc-power-domains". This property is defined for all
dynamically reconfigurable platform nodes. The "ibm,drc-info" elements
are intended to provide a more compact representation, and reduce some
search overhead.
"ibm,dynamic-memory-v2": This property replaces the "ibm,dynamic-memory"
node representation within the "ibm,dynamic-reconfiguration-memory"
property provided by the BMC. This element format is intended to provide
a more compact representation of memory, especially, for systems with
massive amounts of RAM. To simplify portability, this property is
converted to the "ibm,dynamic-memory" property during system boot.
"ibm,architecture.vec": Bidirectional communication mechanism between
the host system and the front end processor indicating what features
the host system supports and what features the front end processor will
actually provide. In this case, we are indicating that the host system
can support the new device tree structures "ibm,drc-info" and
"ibm,dynamic-memory-v2".
[V1: Initial presentation of PAPR 2.7 changes to device tree.]
[V2: Revise constant names. Fix some syntax errors. Improve comments.]
[V3: Revise tests for presence of new properties to always scan devicetree
instead of depending upon architecture vec, due to reboot issues.]
[V4: Rearrange some code changes in patches to better match application,
and other code cleanup.]
[V5: Resynchronize patches.]
[V6: Resync to latest kernel commit code]
[V7: Correct mail threading]
[v8: Insert more useful variable names]
Signed-off-by: Michael Bringmann <mwb@linux.vnet.ibm.com>
---
Michael Bringmann (8):
powerpc/firmware: Add definitions for new firmware features.
powerpc/memory: Parse new memory property to register blocks.
powerpc/memory: Parse new memory property to initialize structures.
pseries/hotplug init: Convert new DRC memory property for hotplug runtime
pseries/drc-info: Search new DRC properties for CPU indexes
hotplug/drc-info: Add code to search new devtree properties
powerpc: Check arch.vec earlier during boot for memory features
powerpc: Enable support for new DRC devtree properties
arch/powerpc/include/asm/firmware.h | 5 -
arch/powerpc/include/asm/prom.h | 38 ++++-
arch/powerpc/kernel/prom.c | 103 +++++++++++--
arch/powerpc/kernel/prom_init.c | 3
arch/powerpc/mm/numa.c | 168 ++++++++++++++++++--
arch/powerpc/platforms/pseries/Makefile | 4
arch/powerpc/platforms/pseries/firmware.c | 2
arch/powerpc/platforms/pseries/hotplug-memory.c | 93 +++++++++++
arch/powerpc/platforms/pseries/pseries_energy.c | 189 ++++++++++++++++++++---
drivers/pci/hotplug/rpadlpar_core.c | 13 +-
drivers/pci/hotplug/rpaphp.h | 4
drivers/pci/hotplug/rpaphp_core.c | 109 ++++++++++---
12 files changed, 628 insertions(+), 103 deletions(-)
--
Michael W. Bringmann
Linux Technology Center
IBM Corporation
mwb@linux.vnet.ibm.com
next reply other threads:[~2016-10-25 21:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 21:32 Michael Bringmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-27 14:24 [PATCH V8 0/8] powerpc/devtree: Add support for 2 new DRC properties Michael Bringmann
2016-10-26 15:23 Michael Bringmann
2016-10-25 22:34 Michael Bringmann
2016-10-25 22:26 Michael Bringmann
2016-10-25 22:21 Michael Bringmann
2016-10-25 22:06 Michael Bringmann
2016-10-25 21:53 Michael Bringmann
2016-10-25 21:46 Michael Bringmann
2016-10-25 21:09 Michael Bringmann
2016-10-25 21:05 Michael Bringmann
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=20161025213117.165626.94076.stgit@powerkvm6.aus.stglabs.ibm.com \
--to=mwb@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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).