On Tue, 2008-05-13 at 09:23 -0700, Geoff Levand wrote: > A change was made to walk_memory_resource() in commit > 4b119e21d0c66c22e8ca03df05d9de623d0eb50f that added a > check of find_lmb(). Add the corresponding lmb_add() > call to ps3_mm_add_memory() so that that check will > succeed. > > This fixes the condition where the PS3 boots up with > just the 128 MiB of boot memory. > > Signed-off-by: Geoff Levand <[EMAIL PROTECTED]> > ---
When you do an lmb_add you should probably also do an lmb_analyze to update the total memory count etc... That leads to some interesting issues such as the LMB stuff wasn't really meant to be dynamically modified after boot, and thus the kernel has no locks in there. That can be an issue... Paul, any thoughts here ? Should we add a lock ? That would mean being careful as the LMB stuff can be called very early, and spinlock wants things like PACA and possibly lockdep to be around.. Ben. > Paul, > > Please send this one upstream at your earliest convenience. > > -Geoff > > arch/powerpc/platforms/ps3/mm.c | 2 ++ > 1 file changed, 2 insertions(+) > > --- a/arch/powerpc/platforms/ps3/mm.c > +++ b/arch/powerpc/platforms/ps3/mm.c > @@ -317,6 +317,8 @@ static int __init ps3_mm_add_memory(void > return result; > } > > + lmb_add(start_addr, map.r1.size); > + > result = online_pages(start_pfn, nr_pages); > > if (result) > > _______________________________________________ > Linuxppc-dev mailing list > Linuxppc-dev@ozlabs.org > https://ozlabs.org/mailman/listinfo/linuxppc-dev _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
