aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorOliver O'Halloran <[email protected]>2016-05-11 19:22:18 +1000
committerMichael Ellerman <[email protected]>2016-06-16 16:03:21 +1000
commit3079abe555511031e2ba5d1e21ddc52edc9af349 (patch)
tree0a7959515a04441f36465eddb58bb843301a5b17 /tools/perf/scripts/python
parentaac6a91fea93e6bdd7ac20365d7ecc9187ca61da (diff)
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 <[email protected]> Reviewed-by: Balbir Singh <[email protected]> Signed-off-by: Michael Ellerman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions