diff options
| author | Scott Wood <scottwood@freescale.com> | 2014-09-18 14:05:02 -0500 |
|---|---|---|
| committer | Scott Wood <scottwood@freescale.com> | 2014-09-19 15:01:05 -0500 |
| commit | 6db35ad2373eed5deb3b105ae7c1e9de3e34ae94 (patch) | |
| tree | 4e38615811beda954fb12fbec69367a80a79d63e /arch/powerpc/platforms/maple | |
| parent | 94105a762016aea3284c07c813017b90a6325f10 (diff) | |
| download | blackbird-op-linux-6db35ad2373eed5deb3b105ae7c1e9de3e34ae94.tar.gz blackbird-op-linux-6db35ad2373eed5deb3b105ae7c1e9de3e34ae94.zip | |
powerpc/mm: Use common paging_init() for NUMA
Commit 1c98025c6c95bc057a25e2c6596de23288c68160 "powerpc: Dynamic DMA
zone limits" updated how zones are created in paging_init(), but missed
the NUMA version of paging_init(). This was noticed via a linker
error, since dma_pfn_limit_to_zone() was, like the non-NUMA
paging_init(), limited by #ifndef CONFIG_NEED_MULTIPLE_NODES.
It turns out that the NUMA paging_init() was not actually doing
anything different from the standard paging_init(), other than a couple
debug prints, a couple 32-bit-only ifdef sections, and a call to
mark_nonram_nosave(). It's not clear whether mark_nonram_nosave() is
inherently wrong to do for NUMA, or just not useful on targets that
have NUMA, but for now I'm preserving the existing behavior.
Fixes: 1c98025c6c9 "powerpc: Dynamic DMA zone limits"
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Scott Wood <scottwood@freescale.com>
Diffstat (limited to 'arch/powerpc/platforms/maple')
0 files changed, 0 insertions, 0 deletions
