Messages in this thread | | | Date | Tue, 04 Mar 2008 15:00:25 +0100 | From | devzero@web ... | Subject | Re: [PATCH 2.6.24] mm: BadRAM support for broken memory |
| |
> > >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.html > > > > someone 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...
> 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? isn`t badram meant to be used together with memtest86 and isn`t 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
| |