Re: linux-next: parsing mem=700M broken

From: Hugh Dickins
Date: Wed Dec 24 2008 - 09:44:18 EST


On Wed, 24 Dec 2008, Rusty Russell wrote:
> On Wednesday 24 December 2008 01:03:27 Ingo Molnar wrote:
> > * Yinghai Lu <yinghai@xxxxxxxxxx> wrote:
> > > On Mon, Dec 22, 2008 at 7:06 PM, Hugh Dickins <hugh@xxxxxxxxxxx> wrote:
> > > >
> > > > I find that bootparam "mem=700M" isn't working in linux-next or mmotm,
> > > > and have bisected it down to your patch below; but now I'm off to bed
> > > > without working out just what goes wrong (I'll bet it's the "=").
(I lost that bet)
>
> Thanks for the report and analysis.
>
> > Rusty, will you fix or revert it?
>
> mem= is actually easy, memmap= is harder. This is tested and pushed.

Thanks, that gets my "mem=700M" respected on x86_32 and x86_64.
But (of course: it's a patch to arch/x86) doesn't help at all on
ppc64; and I presume other architectures also remain broken...

Hugh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/