Following the RFC for the BadRAM feature here's the updated version with spelling fixes, thanks go to Randy Dunlap. Also the code is now less verbose, as requested by Andi Kleen. v2 with even more spelling fixes suggested by Randy. Patches are against vanilla 2.6.39. 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 The concerning pages are then marked with the hwpoison flag and thus won't be used by the memory managment system. Link to Ricks original patches and docs: http://rick.vanrein.org/linux/badram/ Stefan Stefan Assmann (3): Add string parsing function get_next_ulong support for broken memory modules (BadRAM) Add documentation and credits for BadRAM CREDITS | 9 + Documentation/BadRAM.txt | 370 +++++++++++++++++++++++++++++++++++ Documentation/kernel-parameters.txt | 6 + include/linux/kernel.h | 1 + lib/cmdline.c | 35 ++++ mm/memory-failure.c | 100 ++++++++++ 6 files changed, 521 insertions(+), 0 deletions(-) create mode 100644 Documentation/BadRAM.txt -- 1.7.4 -- 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>