From: Simon Horman <horms@verge.net.au>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: linuxppc-dev@lists.ozlabs.org, kexec@lists.infradead.org,
vgoyal@redhat.com
Subject: Re: [PATCH] ppc64: increase TREEWORDS value in ppc64
Date: Fri, 10 Sep 2010 10:43:07 +0900 [thread overview]
Message-ID: <20100910014307.GF8477@verge.net.au> (raw)
In-Reply-To: <20100909202711.GA22581@hmsreliant.think-freely.org>
[ Repost with correct kexec ML address ]
[ CCed linuxppc-dev ]
On Thu, Sep 09, 2010 at 04:27:11PM -0400, Neil Horman wrote:
> hey-
> Got a segfault recently on ppc64 kexec with a system with 256Gb of ram.
> Tracked it back to running over the end of the device tree buffer that we have
> allocated. I can't find any docs on how big the device tree can legally be, so
> for now I figure just upping its size is sufficient. Confirmed that this fixed
> the segfault.
Thanks Neil, though it would be nice to know what the limit actually is.
I'll hold off on applying this for a few days to see of the PPC people
have any comments on that.
>
> Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
>
>
> fs2dt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
> diff --git a/kexec/arch/ppc/fs2dt.c b/kexec/arch/ppc/fs2dt.c
> index 238a3f2..2f0f937 100644
> --- a/kexec/arch/ppc/fs2dt.c
> +++ b/kexec/arch/ppc/fs2dt.c
> @@ -33,7 +33,7 @@
>
> #define MAXPATH 1024 /* max path name length */
> #define NAMESPACE 16384 /* max bytes for property names */
> -#define TREEWORDS 65536 /* max 32 bit words for properties */
> +#define TREEWORDS 131070 /* max 32 bit words for properties */
> #define MEMRESERVE 256 /* max number of reserved memory blks */
> #define MAX_MEMORY_RANGES 1024
> #define COMMAND_LINE_SIZE 512 /* from kernel */
prev parent reply other threads:[~2010-09-10 2:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100909202711.GA22581@hmsreliant.think-freely.org>
2010-09-10 1:41 ` [PATCH] ppc64: increase TREEWORDS value in ppc64 Simon Horman
2010-09-10 1:43 ` Simon Horman [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=20100910014307.GF8477@verge.net.au \
--to=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nhorman@tuxdriver.com \
--cc=vgoyal@redhat.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).