mm: BadRAM support for broken memory
Quoted 9 lines
Quoted 7 lines
Quoted 1 line
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.htmlsomeone 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
sorry, but maybe that reply was sent off-list ? at least i cannot find that in the archive...
Quoted 4 lines
acceptable for upstream to merge an easier to use boot option - be that badmem=addr$size or excludemem=addr$size. Please send a patch :-)
Ingo
easier to use option? isnt badram meant to be used together with memtest86 and isnt that patterns generated by memtest86 already meant to provide a highly efficient way to specify bad memory regions ? i don`t see where there is room for optimization here. see that slightly outdate linuxjournal article at http://www.linuxjournal.com/article/4489
or the "Capturing errors in a pattern" chapter inside the patch.
regards
roland
_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066