| 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
| ||
|
Message-ID: <4E023142.1080605@zytor.com> Date: Wed, 22 Jun 2011 11:15:30 -0700 From: "H. Peter Anvin" <hpa@...or.com> To: Stefan Assmann <sassmann@...nic.de> CC: linux-mm@...ck.org, linux-kernel@...r.kernel.org, akpm@...ux-foundation.org, tony.luck@...el.com, andi@...stfloor.org, mingo@...e.hu, rick@...rein.org, rdunlap@...otime.net Subject: Re: [PATCH v2 0/3] support for broken memory modules (BadRAM) On 06/22/2011 04:18 AM, Stefan Assmann wrote: > > The idea is to allow the user to specify RAM addresses that shouldn't be > touched by the OS, because they are broken in some way. Not all machines have > hardware support for hwpoison, ECC RAM, etc, so here's a solution that allows to > use bitmasks to mask address patterns with the new "badram" kernel command line > parameter. > Memtest86 has an option to generate these patterns since v2.3 so the only thing > for the user to do should be: > - run Memtest86 > - note down the pattern > - add badram=<pattern> to the kernel command line > We already support the equivalent functionality with memmap=<address>$<length> for those with only a few ranges... this has been supported for ages, literally. For those with a lot of ranges, like Google, the command line is insufficient. -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/
Powered by blists - more mailing lists