Re: x86: memtest bootparam

From: Yinghai Lu
Date: Sat Apr 19 2008 - 16:54:24 EST


On Sat, Apr 19, 2008 at 6:33 AM, Pavel Machek <pavel@xxxxxx> wrote:
> Hi!
>
>
> > Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx> wrote:
> >
> > > Gitweb: http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c64df70793a9c344874eb4af19f85e0662d2d3ee
> > > Commit: c64df70793a9c344874eb4af19f85e0662d2d3ee
> > > Parent: 9b967106da0357ef8b08847dce35584a04134f20
> > > Author: Yinghai Lu <yhlu.kernel.send@xxxxxxxxx>
> > > AuthorDate: Fri Mar 21 18:56:19 2008 -0700
> > > Committer: Ingo Molnar <mingo@xxxxxxx>
> > > CommitDate: Thu Apr 17 17:41:21 2008 +0200
> > >
> > > x86: memtest bootparam
> > >
> > > ...
> > >
> > >
> > > + memtest= [KNL,X86_64] Enable memtest
> > > + Format: <integer>
> > > + range: 0,4 : pattern number
> > > + default : 0 <disable>
> >
> > OK. Did the new memtest feature get documented anywhere, btw? I'm only
> > vaguely aware of its existence.
>
> Actually it would be nice if memtest was global, not x86-specific,
> feature.
>
> I had some fun with arm running with 256mb, when only 128mb was
> present. It booted succesfully...

depends if you have find_e820_area_size in you platform. that need
reserve_early...

maybe we need to make reserve_early generic at first.

YH
--
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/