From: Michael Ellerman <[EMAIL PROTECTED]>
Date: Mon, 18 Aug 2008 12:00:32 +1000
> Although I can't find a system with holes (the newer hypervisors make
> things look contiguous I think), so I can't really test the interesting
> case.
I have several so I'll make sure it works in such cases :)
___
On Fri, 2008-08-15 at 19:57 -0700, David Miller wrote:
> From: Michael Ellerman <[EMAIL PROTECTED]>
> Date: Sat, 16 Aug 2008 10:46:22 +1000
>
> > On Fri, 2008-08-15 at 15:25 -0700, David Miller wrote:
> > > Sounds great. Mind if I push the following to Linus?
> >
> > Looks good to me.
> >
> > I
From: Michael Ellerman <[EMAIL PROTECTED]>
Date: Sat, 16 Aug 2008 10:46:22 +1000
> On Fri, 2008-08-15 at 15:25 -0700, David Miller wrote:
> > Sounds great. Mind if I push the following to Linus?
>
> Looks good to me.
>
> I'll test it on Monday. I don't know if I have a system with memory
> hole
On Fri, 2008-08-15 at 15:25 -0700, David Miller wrote:
> From: Michael Ellerman <[EMAIL PROTECTED]>
> Date: Thu, 14 Aug 2008 21:26:53 +1000
>
> > Perhaps after the first loop we should set memory_limit to equal
> > lmb_end_of_DRAM(), then the second loop should work as it is.
>
> Sounds great. M
From: Michael Ellerman <[EMAIL PROTECTED]>
Date: Thu, 14 Aug 2008 21:26:53 +1000
> Perhaps after the first loop we should set memory_limit to equal
> lmb_end_of_DRAM(), then the second loop should work as it is.
Sounds great. Mind if I push the following to Linus?
lmb: Fix reserved region handl
On Thu, 2008-08-14 at 01:20 -0700, David Miller wrote:
> I just mentioned this to Ben H. on IRC and promised I would report it
> here. :-)
>
> The first loop over lmb.memory in this function interprets the
> memory_limit as a raw size limit, and that's fine so far.
>
> But the second loop over lm
