[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110310064614.GE9289@elte.hu>
Date: Thu, 10 Mar 2011 07:46:14 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc: Yinghai Lu <yinghai@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Russell King <linux@....linux.org.uk>,
David Miller <davem@...emloft.net>, Tejun Heo <tj@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH/v2] mm/memblock: Properly handle overlaps and fix error
path
* Benjamin Herrenschmidt <benh@...nel.crashing.org> wrote:
> On Wed, 2011-03-09 at 12:41 -0800, Yinghai Lu wrote:
> > > Hopefully not damaged with a spurious bit of email header this
> > > time around... sorry about that.
> >
> > works on my setups...
> >
> > [ 0.000000] Subtract (26 early reservations)
> > [ 0.000000] [000009a000-000009efff]
> > [ 0.000000] [000009f400-00000fffff]
> > [ 0.000000] [0001000000-0003495048]
> > ...
> > before:
> > [ 0.000000] Subtract (27 early reservations)
> > [ 0.000000] [000009a000-000009efff]
> > [ 0.000000] [000009f400-00000fffff]
> > [ 0.000000] [00000f85b0-00000f86b3]
> > [ 0.000000] [0001000000-0003495048]
>
> Ah interesting, so you did have a case of overlap that wasn't properly
> handled as well.
>
> If there is no objection, I'll queue that up in powerpc-next for the
> upcoming merge window (soon now).
I think it would be better to do it via -mm, as x86 and other architectures are now
affected by memblock changes as well.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists