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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 21 Apr 2008 16:17:35 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Yinghai Lu <yhlu.kernel@...il.com>
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


* 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?

	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/