Searched hist:fb6d73d3014babb69f5cc2d1d78b31e9d09fc5df (Results 1 – 2 of 2) sorted by relevance
/linux/arch/powerpc/mm/ |
H A D | numa.c | diff fb6d73d3014babb69f5cc2d1d78b31e9d09fc5df Wed Nov 16 01:43:26 CET 2005 Paul Mackerras <paulus@samba.org> [PATCH] powerpc: Fix sparsemem with memory holes [was Re: ppc64 oops..]
This patch should fix the crashes we have been seeing on 64-bit powerpc systems with a memory hole when sparsemem is enabled. I'd appreciate it if people who know more about NUMA and sparsemem than me could look over it.
There were two bugs. The first was that if NUMA was enabled but there was no NUMA information for the machine, the setup_nonnuma() function was adding a single region, assuming memory was contiguous. The second was that the loops in mem_init() and show_mem() assumed that all pages within the span of a pgdat were valid (had a valid struct page).
I also fixed the incorrect setting of num_physpages that Mike Kravetz pointed out.
Signed-off-by: Paul Mackerras <paulus@samba.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
|
H A D | mem.c | diff fb6d73d3014babb69f5cc2d1d78b31e9d09fc5df Wed Nov 16 01:43:26 CET 2005 Paul Mackerras <paulus@samba.org> [PATCH] powerpc: Fix sparsemem with memory holes [was Re: ppc64 oops..]
This patch should fix the crashes we have been seeing on 64-bit powerpc systems with a memory hole when sparsemem is enabled. I'd appreciate it if people who know more about NUMA and sparsemem than me could look over it.
There were two bugs. The first was that if NUMA was enabled but there was no NUMA information for the machine, the setup_nonnuma() function was adding a single region, assuming memory was contiguous. The second was that the loops in mem_init() and show_mem() assumed that all pages within the span of a pgdat were valid (had a valid struct page).
I also fixed the incorrect setting of num_physpages that Mike Kravetz pointed out.
Signed-off-by: Paul Mackerras <paulus@samba.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
|