From: Michael Ellerman <mpe@ellerman•id.au>
To: dwalker@fifo99•com, Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: Paul Mackerras <paulus@samba•org>, linuxppc-dev@lists•ozlabs.org
Subject: Re: simple_alloc space tramples initrd
Date: Mon, 11 Jan 2016 14:09:34 +1100 [thread overview]
Message-ID: <1452481774.31943.3.camel@ellerman.id.au> (raw)
In-Reply-To: <20160108174506.GA12105@fifo99.com>
On Fri, 2016-01-08 at 09:45 -0800, dwalker@fifo99•com wrote:
> Hi,
>
> A powerpc machine I'm working on has this problem where the
> simple_alloc_init() area is trampling the initrd. The two are placed fairly
> close together.
Which machine / platform?
> I have a fix for this proposed to add a section into
> arch/powerpc/boot/zImage.lds.S called "mallocarea" to account for this space,
> but not all powerpc platforms use simple_alloc_init(). So for those platforms
> it's a waste.
Yeah I don't really like the sound of that. We could do it if it was behind a
CONFIG option, but hopefully there is a better solution.
> Another alternative is to alter the bootloader to place more space between
> the kernel image and initrd image.
>
> I wanted to get some feedback on the right way to fix this. It seems like it
> could be a generic issue on powerpc, or it's possibly already fixed someplace
> and I just haven't noticed.
I don't really know that code very well. But ideally either the boot loader
gives you space, or the platform boot code is smart enough to detect that there
is insufficient room and puts the heap somewhere else.
cheers
next prev parent reply other threads:[~2016-01-11 3:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 17:45 simple_alloc space tramples initrd dwalker
2016-01-11 3:09 ` Michael Ellerman [this message]
2016-01-11 16:49 ` dwalker
2016-01-11 22:17 ` Michael Ellerman
2016-01-11 23:07 ` dwalker
2016-01-11 23:37 ` Michael Ellerman
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=1452481774.31943.3.camel@ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=benh@kernel$(echo .)crashing.org \
--cc=dwalker@fifo99$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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