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, 8 Mar 2008 12:13:01 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	"H. Peter Anvin" <hpa@...or.com>
cc:	Ingo Molnar <mingo@...e.hu>, devzero@....de, pavel@....cz,
	linux-kernel@...r.kernel.org, rick@...rein.org
Subject: Re: [PATCH 2.6.24] mm: BadRAM support for broken memory

On Sat, 8 Mar 2008, H. Peter Anvin wrote:

> > 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.)

I admit that I haven't examined badram too closely, but I think that what 
it has in addition to what you can get by simple 'memmap=..' is that it 
allows you to use bitmasks to mask particular address patterns.

-- 
Jiri Kosina
SUSE Labs

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