aboutsummaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorDave Hansen <dave@linux.vnet.ibm.com>2008-12-09 08:21:33 +0000
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>2009-01-08 16:25:08 +1100
commit5d21ea2b0e1d9d5d880670dbb9a96efe9b419583 (patch)
tree10f427695e940778473c3ec350ae8e5e34eb8288 /arch
parentc555e520ef794a94dc36a8ded93ece6369ff7ca0 (diff)
powerpc/mm:: Cleanup careful_allocation(): bootmem already panics
If we fail a bootmem allocation, the bootmem code itself panics. No need to redo it here. Also change the wording of the other panic. We don't strictly have to allocate memory on the specified node. It is just a hint and that node may not even *have* any memory on it. In that case we can and do fall back to other nodes. Signed-off-by: Dave Hansen <dave@linux.vnet.ibm.com> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'arch')
-rw-r--r--arch/powerpc/mm/numa.c6
1 files changed, 1 insertions, 5 deletions
diff --git a/arch/powerpc/mm/numa.c b/arch/powerpc/mm/numa.c
index 213664c9cdc..aabf30175eb 100644
--- a/arch/powerpc/mm/numa.c
+++ b/arch/powerpc/mm/numa.c
@@ -836,7 +836,7 @@ static void __init *careful_allocation(int nid, unsigned long size,
ret = __lmb_alloc_base(size, align, lmb_end_of_DRAM());
if (!ret)
- panic("numa.c: cannot allocate %lu bytes on node %d",
+ panic("numa.c: cannot allocate %lu bytes for node %d",
size, nid);
/*
@@ -856,10 +856,6 @@ static void __init *careful_allocation(int nid, unsigned long size,
ret = (unsigned long)__alloc_bootmem_node(NODE_DATA(new_nid),
size, align, 0);
- if (!ret)
- panic("numa.c: cannot allocate %lu bytes on node %d",
- size, new_nid);
-
ret = __pa(ret);
dbg("alloc_bootmem %lx %lx\n", ret, size);