Date: Tue, 04 Mar 2008 15:00:25 +0100
Message-Id: <182375432@web.de>
MIME-Version: 1.0
From: devzero@web.de
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org, pavel@ucw.cz, rick@vanrein.org
Subject: Re: [PATCH 2.6.24] mm: BadRAM support for broken memory
Organization: http://freemail.web.de/
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1498
Lines: 35

> > >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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/