linux-kernel - Re: x86: memtest bootparam

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <86802c440804210938w8e401fg11d4aaa5646cce8a@mail.gmail.com>
Date:	Mon, 21 Apr 2008 09:38:44 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	"Pavel Machek" <pavel@....cz>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Yinghai Lu" <yhlu.kernel.send@...il.com>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: x86: memtest bootparam

On Mon, Apr 21, 2008 at 7:17 AM, Ingo Molnar <mingo@...e.hu> wrote:
>
> * Yinghai Lu <yhlu.kernel@...il.com> wrote:
>
> > >  > 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.
>
> e820 is very x86 specific - i think the proper interface would be to
> move the memtest feature to the bootmem subsystem. I.e. to run it once
> all the early reservations have been flushed into bootmem - but before
> we free all bootmem pages into the page allocator.
>
> this still leaves a rather large amount of RAM to be tested, and keeps
> it all cross-arch as well. Hm?

sounds good, and arch part only need to check region that bootdata use
for bootmem allocation.

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