From: Michael Ellerman <mpe@ellerman.id.au>
To: Oliver O'Halloran <oohall@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: linux-mm@kvack.org, Oliver O'Halloran <oohall@gmail.com>
Subject: Re: [v2] powerpc/mm: Ensure "special" zones are empty
Date: Tue, 21 Jun 2016 10:40:53 +1000 (AEST) [thread overview]
Message-ID: <3rYTRT6gDSz9t0f@ozlabs.org> (raw)
In-Reply-To: <1462958539-25552-1-git-send-email-oohall@gmail.com>
On Wed, 2016-11-05 at 09:22:18 UTC, Oliver O'Halloran wrote:
> The mm zone mechanism was traditionally used by arch specific code to
> partition memory into allocation zones. However there are several zones
> that are managed by the mm subsystem rather than the architecture. Most
> architectures set the max PFN of these special zones to zero, however on
> powerpc we set them to ~0ul. This, in conjunction with a bug in
> free_area_init_nodes() results in all of system memory being placed in
> ZONE_DEVICE when enabled. Device memory cannot be used for regular kernel
> memory allocations so this will cause a kernel panic at boot. Given the
> planned addition of more mm managed zones (ZONE_CMA) we should aim to be
> consistent with every other architecture and set the max PFN for these
> zones to zero.
>
> Signed-off-by: Oliver O'Halloran <oohall@gmail.com>
> Reviewed-by: Balbir Singh <bsingharora@gmail.com>
> Cc: linux-mm@kvack.org
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/3079abe555511031e2ba5d1e21
cheers
next prev parent reply other threads:[~2016-06-21 0:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 7:54 [PATCH v2 1/2] powerpc/mm: define TOP_ZONE as a constant Oliver O'Halloran
2016-05-05 7:54 ` [PATCH v2 2/2] powerpc/mm: Ensure "special" zones are empty Oliver O'Halloran
2016-05-09 23:55 ` [v2,2/2] " Michael Ellerman
2016-05-11 7:11 ` Balbir Singh
2016-05-11 9:22 ` [PATCH v2] " Oliver O'Halloran
2016-06-21 0:40 ` Michael Ellerman [this message]
2016-05-10 21:48 ` [v2,1/2] powerpc/mm: define TOP_ZONE as a constant 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=3rYTRT6gDSz9t0f@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oohall@gmail.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).