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

[H. Peter Anvin]

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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/