From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Meelis Roos <mroos@linux.ee>, Christophe Leroy <christophe.leroy@c-s.fr>
Cc: Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Scott Wood <oss@buserror.net>,
Balbir Singh <bsingharora@gmail.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] powerpc: fix boot on BOOK3S_32 with CONFIG_STRICT_KERNEL_RWX
Date: Wed, 22 Nov 2017 09:22:51 +1100 [thread overview]
Message-ID: <1511302971.2466.26.camel@kernel.crashing.org> (raw)
In-Reply-To: <alpine.LRH.2.21.1711211821320.8798@math.ut.ee>
On Tue, 2017-11-21 at 19:28 +0200, Meelis Roos wrote:
> For wider powerpc audience: this warning-like INFO bit is present
> independently of theis patch. Is it dangerous for some configuration?
>
> INFO: Uncompressed kernel (size 0x5d6c54) overlaps the address of the wrapper(0x400000)
> INFO: Fixing the link_address of wrapper to (0x600000)
Mostly means you need more memory than the old default... I don't think
it's an issue unless you are hitting very small systems or your OF
implementation has that memory occupied.
Ben.
next prev parent reply other threads:[~2017-11-21 22:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 14:28 [PATCH v2] powerpc: fix boot on BOOK3S_32 with CONFIG_STRICT_KERNEL_RWX Christophe Leroy
2017-11-21 17:28 ` Meelis Roos
2017-11-21 22:22 ` Benjamin Herrenschmidt [this message]
2017-11-21 23:07 ` Balbir Singh
2017-11-21 23:07 ` Balbir Singh
2017-11-22 7:16 ` Christophe LEROY
2017-11-22 7:16 ` Christophe LEROY
2017-11-22 11:48 ` Michael Ellerman
2017-11-22 11:48 ` Michael Ellerman
2017-11-23 7:49 ` Christophe LEROY
2017-11-23 7:49 ` Christophe LEROY
2017-11-23 12:04 ` Michael Ellerman
2017-11-23 12:04 ` Michael Ellerman
2017-11-25 23:57 ` Balbir Singh
2017-11-25 23:57 ` Balbir Singh
2017-11-22 11:55 ` Michael Ellerman
2017-11-24 9:46 ` [v2] " Michael Ellerman
-- strict thread matches above, loose matches on Subject: below --
2017-11-21 14:26 [PATCH v2] " Christophe Leroy
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=1511302971.2466.26.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=bsingharora@gmail.com \
--cc=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=mroos@linux.ee \
--cc=oss@buserror.net \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.