Re: lmb_alloc() and page memory overlap

2011-11-30 Thread Benjamin Herrenschmidt
> > This should have been fixed in memblock in recent kernel, at least I > > believe it is. It looks like this is caused by overlapping lmb_reserve() > > at boot (or lmb_reserve() overlapping an lmb_alloc'ated region which > > boils down to the same thing). > > > > Old lmb didn't deal with that we

Re: lmb_alloc() and page memory overlap

2011-11-30 Thread Prashant Bhole
On Thu, Dec 1, 2011 at 9:30 AM, Benjamin Herrenschmidt wrote: > On Tue, 2011-11-29 at 18:51 +0530, Prashant Bhole wrote: >> Hi, >> I am using custom 460ex board with kernel version 2.6.30. >> I noticed that page_alloc() is returning a page whose memory >> is already allocated by lmb_alloc() while

Re: lmb_alloc() and page memory overlap

2011-11-30 Thread Benjamin Herrenschmidt
On Tue, 2011-11-29 at 18:51 +0530, Prashant Bhole wrote: > Hi, > I am using custom 460ex board with kernel version 2.6.30. > I noticed that page_alloc() is returning a page whose memory > is already allocated by lmb_alloc() while unflattening the device > tree. As per my knowledge the memory alloca

lmb_alloc() and page memory overlap

2011-11-29 Thread Prashant Bhole
Hi, I am using custom 460ex board with kernel version 2.6.30. I noticed that page_alloc() is returning a page whose memory is already allocated by lmb_alloc() while unflattening the device tree. As per my knowledge the memory allocated by lmb_alloc() should be reserved till the end, right? Some mo