powerpc/mm: Drop dump_numa_memory_topology()
authorMichael Ellerman <mpe@ellerman.id.au>
Thu, 13 Oct 2016 05:27:30 +0000 (16:27 +1100)
committerMichael Ellerman <mpe@ellerman.id.au>
Wed, 19 Oct 2016 09:35:40 +0000 (20:35 +1100)
commit08b5e79ebdb58868cbb6976ba0e3898029394e6d
tree32aeb52a0eaa41e558de394b72af36056bf72365
parent70b565bbdb911023373e035225ab10077e4ab937
powerpc/mm: Drop dump_numa_memory_topology()

At boot we dump the NUMA memory topology in dump_numa_memory_topology(),
at KERN_DEBUG level, resulting in output like:

  Node 0 Memory: 0x0-0x100000000
  Node 1 Memory: 0x100000000-0x200000000

Which is nice enough, but immediately after that we iterate over each
node and call setup_node_data(), which also prints out the node ranges,
at KERN_INFO, giving eg:

  numa: Initmem setup node 0 [mem 0x00000000-0xffffffff]
  numa: Initmem setup node 1 [mem 0x100000000-0x1ffffffff]

Additionally dump_numa_memory_topology() does not use KERN_CONT
correctly, resulting in split output lines on recent kernels.

So drop dump_numa_memory_topology() as superfluous chatter.

Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Acked-by: Balbir Singh <bsingharora@gmail.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
arch/powerpc/mm/numa.c