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, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>