Thread (41 messages) 41 messages, 12 authors, 2011-06-24

Re: [PATCH v2 0/3] support for broken memory modules (BadRAM)

From: Stefan Assmann <hidden>
Date: 2011-06-23 14:08:43
Also in: lkml

On 23.06.2011 15:39, Matthew Garrett wrote:
On Wed, Jun 22, 2011 at 01:18:51PM +0200, Stefan Assmann wrote:
quoted
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.
Repost with LKML in Cc as suggested by Andrew Morton.
Would it be more reasonable to do this in the bootloader? You'd ideally 
want this to be done as early as possible in order to avoid awkward 
situations like your ramdisk ending up in the bad RAM area.
Not sure what exactly you are suggesting here. The kernel somehow needs
to know what memory areas to avoid so we supply this information via
kernel command line.
What the bootloader could do is to allow the kernel/initrd to be loaded
at an alternative address. That's briefly mentioned in the BadRAM
Documentation as well. Is that what you mean or am I missing something?

  Stefan

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  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@kvack.org"> email@kvack.org </a>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help