Thread (3 messages) flat view 3 messages, 2 authors, 2011-05-12

Re: powerpc: Make early memory scan more resilient to out of order nodes

From: Milton Miller <hidden>
Date: 2011-05-12 08:09:49

On Wed, 11 May 2011 about 20:58:18 -0000, Benjamin Herrenschmidt wrote:
We keep track of the size of the lowest block of memory and call
setup_initial_memory_limit() only after we've parsed them all
Good, we lose our sensitivity to device node ordering.
quoted hunk ↗ jump to hunk
diff --git a/arch/powerpc/kernel/prom.c b/arch/powerpc/kernel/prom.c
quoted hunk ↗ jump to hunk
index 584b398..27475c6 100644
--- a/arch/powerpc/kernel/prom.c
+++ b/arch/powerpc/kernel/prom.c
@@ -70,6 +70,7 @@ int __initdata iommu_force_on;
 unsigned long tce_alloc_start, tce_alloc_end;
 u64 ppc64_rma_size;
 #endif
+static phys_addr_t first_memblock_size;
__initdata 

(its only referenced by 2 __init functions)

Acked-by: Milton Miller <redacted>

 static int __init early_parse_mem(char *p)
 {
..
quoted hunk ↗ jump to hunk
@@ -507,11 +508,14 @@ void __init early_init_dt_add_memory_arch(u64 base, u64 size)
..
quoted hunk ↗ jump to hunk
@@ -708,6 +712,7 @@ void __init early_init_devtree(void *params)
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help