From: Nathan Fontenot <nfont@linux.vnet.ibm.com>
To: Michael Bringmann <mwb@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH V9 8/8] powerpc: Enable support for new DRC devtree properties
Date: Mon, 12 Dec 2016 09:40:37 -0600 [thread overview]
Message-ID: <c0cb1efb-dfcf-0e98-92f8-67a388ca7948@linux.vnet.ibm.com> (raw)
In-Reply-To: <148109495293.193207.8739036690257904427.stgit@powerkvm6.aus.stglabs.ibm.com>
On 12/07/2016 01:16 AM, Michael Bringmann wrote:
> prom_init.c: Enable support for new DRC device tree properties
> "ibm,drc-info" and "ibm,dynamic-memory-v2" in initial handshake
> between the Linux kernel and the front end processor.
>
> Signed-off-by: Michael Bringmann <mwb@linux.vnet.ibm.com>
Reviewed-by: Nathan Fontenot <nfont@linux.vnet.ibm.com>
> ---
> arch/powerpc/kernel/prom_init.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/kernel/prom_init.c b/arch/powerpc/kernel/prom_init.c
> index 88ac964..6e6454f 100644
> --- a/arch/powerpc/kernel/prom_init.c
> +++ b/arch/powerpc/kernel/prom_init.c
> @@ -696,7 +696,7 @@ static void __init early_cmdline_parse(void)
> OV4_MIN_ENT_CAP, /* minimum VP entitled capacity */
>
> /* option vector 5: PAPR/OF options */
> - VECTOR_LENGTH(21), /* length */
> + VECTOR_LENGTH(22), /* length */
> 0, /* don't ignore, don't halt */
> OV5_FEAT(OV5_LPAR) | OV5_FEAT(OV5_SPLPAR) | OV5_FEAT(OV5_LARGE_PAGES) |
> OV5_FEAT(OV5_DRCONF_MEMORY) | OV5_FEAT(OV5_DONATE_DEDICATE_CPU) |
> @@ -732,6 +732,7 @@ static void __init early_cmdline_parse(void)
> 0, /* Byte 19 */
> 0, /* Byte 20 */
> OV5_FEAT(OV5_SUB_PROCESSORS), /* Byte 21 */
> + OV5_FEAT(OV5_DYN_MEM_V2) | OV5_FEAT(OV5_DRC_INFO), /* Byte 22 */
>
> /* option vector 6: IBM PAPR hints */
> VECTOR_LENGTH(3), /* length */
>
next prev parent reply other threads:[~2016-12-12 15:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 7:13 [PATCH V9 0/8] powerpc/devtree: Add support for 2 new DRC properties Michael Bringmann
2016-12-07 7:14 ` [PATCH V9 1/8] powerpc/firmware: Add definitions for new firmware features Michael Bringmann
2016-12-12 15:19 ` Nathan Fontenot
2016-12-07 7:14 ` [PATCH V9 2/8] powerpc/memory: Parse new memory property to register blocks Michael Bringmann
2016-12-12 15:24 ` Nathan Fontenot
2016-12-07 7:14 ` [PATCH V9 3/8] powerpc/memory: Parse new memory property to initialize structures Michael Bringmann
2016-12-12 15:27 ` Nathan Fontenot
2016-12-07 7:14 ` [PATCH V9 4/8] pseries/hotplug init: Convert new DRC memory property for hotplug runtime Michael Bringmann
2016-12-12 15:29 ` Nathan Fontenot
2017-01-31 2:53 ` Michael Ellerman
2017-02-01 16:27 ` [PATCH V10 " Michael Bringmann
2016-12-07 7:15 ` [PATCH V9 5/8] pseries/drc-info: Search new DRC properties for CPU indexes Michael Bringmann
2016-12-07 7:15 ` [PATCH V9 6/8] hotplug/drc-info: Add code to search new devtree properties Michael Bringmann
2016-12-12 15:39 ` Nathan Fontenot
2016-12-07 7:15 ` [PATCH V9 7/8] powerpc: Check arch.vec earlier during boot for memory features Michael Bringmann
2016-12-12 15:39 ` Nathan Fontenot
2016-12-07 7:16 ` [PATCH V9 8/8] powerpc: Enable support for new DRC devtree properties Michael Bringmann
2016-12-12 15:40 ` Nathan Fontenot [this message]
2017-01-24 19:41 ` [PATCH V9 0/8] powerpc/devtree: Add support for 2 new DRC properties 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=c0cb1efb-dfcf-0e98-92f8-67a388ca7948@linux.vnet.ibm.com \
--to=nfont@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mwb@linux.vnet.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).