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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 06/24/2011 09:56 AM, Rick van Rein wrote:
> Hello,
> 
>> Does it scale? [...] Perhaps we may end up with a composite solution. 
> 
> If I had my way, there would be an extension to the e820 format to allow
> the BadRAM patterns to be specified.  Since the extension with bad page
> information is specific to boot loader interaction, this would work in
> exactly those cases that are covered by the current situation.
> 

Yes, a different table might be worthwhile.

Another question, however, is what does this look like at runtime.  In
particular, if I'm not mistaken hwpoison will create struct pages for
these non-memory pages, which seems undesirable...

	-hpa

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


[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]