linux-kernel - Re: [PATCH 2.6.24] mm: BadRAM support for broken memory

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:	Sat, 08 Mar 2008 11:27:12 +0100
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	devzero@....de, pavel@....cz, linux-kernel@...r.kernel.org,
	rick@...rein.org
Subject: Re: [PATCH 2.6.24] mm: BadRAM support for broken memory

Ingo Molnar wrote:
> * devzero@....de <devzero@....de> wrote:
> 
>>> What is wrong with mem=exactmap?
>> probably no ordinary user knows how to use it instead of badram?
>> http://lists.opensuse.org/opensuse/2007-04/msg00501.html
>>
>> someone please show us how to use that instead of badram or how this 
>> can replace what badram does.
> 
> as i said it in another reply to this thread, it would be perfectly 
> acceptable for upstream to merge an easier to use boot option - be that 
> badmem=addr$size or excludemem=addr$size. Please send a patch :-)
> 

It already called:

	memmap=addr$size


... and has been implemented for years.  Does the badram patch do 
anything different?  (And yes, I agree the $/@/# is ugly.)

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