diff options
| author | Oliver O'Halloran | 2016-05-11 11:22:18 +0200 |
|---|---|---|
| committer | Michael Ellerman | 2016-06-16 08:03:21 +0200 |
| commit | 3079abe555511031e2ba5d1e21ddc52edc9af349 (patch) | |
| tree | 0a7959515a04441f36465eddb58bb843301a5b17 /.get_maintainer.ignore | |
| parent | powerpc/asm: Remove unused symbols in asm-offsets.c (diff) | |
| download | kernel-qcow2-linux-3079abe555511031e2ba5d1e21ddc52edc9af349.tar.gz kernel-qcow2-linux-3079abe555511031e2ba5d1e21ddc52edc9af349.tar.xz kernel-qcow2-linux-3079abe555511031e2ba5d1e21ddc52edc9af349.zip | |
powerpc/mm: Ensure "special" zones are empty
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>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to '.get_maintainer.ignore')
0 files changed, 0 insertions, 0 deletions