From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: praveen.pandey@in.ibm.com, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: powerpc/prom: Increase RMA size to 512MB
Date: Thu, 6 Apr 2017 23:06:03 +1000 (AEST) [thread overview]
Message-ID: <3vzNHv1ZFfz9s8T@ozlabs.org> (raw)
In-Reply-To: <20170330040349.GA31756@us.ibm.com>
On Thu, 2017-03-30 at 04:03:49 UTC, Sukadev Bhattiprolu wrote:
> >From 3ae8d1ed31b01b92b172fe20e4560cfbfab135ec Mon Sep 17 00:00:00 2001
> From: root <root@furatripa-lp2.aus.stglabs.ibm.com>
> Date: Mon, 27 Mar 2017 19:43:14 -0400
> Subject: [PATCH] powerpc/prom: Increase RMA size to 512MB
>
> When booting very large systems with a large initrd, we run out of
> space for either the RTAS or the flattened device tree (FDT). Boot
> fails with messages like:
>
> Could not allocate memory for RTAS
> or
> No memory for flatten_device_tree (no room)
>
> Increasing the minimum RMA size to 512MB fixes the problem. This
> should not have an impact on smaller LPARs (with 256MB memory),
> as the firmware will cap the RMA to the memory assigned to the LPAR.
>
> Fix is based on input/discussions with Michael Ellerman. Thanks to
> Praveen K. Pandey for testing on a large system.
>
> Reported-by: Praveen K. Pandey <preveen.pandey@in.ibm.com>
> Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/687da8fce1682c9f1e87530e731189
cheers
prev parent reply other threads:[~2017-04-06 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 4:03 [PATCH] powerpc/prom: Increase RMA size to 512MB Sukadev Bhattiprolu
2017-04-06 13:06 ` Michael Ellerman [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=3vzNHv1ZFfz9s8T@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=praveen.pandey@in.ibm.com \
--cc=sukadev@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).