Re: marching through all physical memory in software

[Chris Friesen]

Valdis.Kletnieks@xxxxxx wrote:
> On Mon, 02 Feb 2009 12:29:45 CST, Chris Friesen said:
>
> > The next question is who handles the conversion of the various different 
> > arch-specific BIOS mappings to a standard format that we can feed to the 
> > background "scrub" code.  Is this something that belongs in the edac 
> > memory controller code, or would it live in /arch/foo somewhere?
>
>
> If it's intended to be something basically stand-alone that doesn't require
> an actual EDAC chipset, it should probably live elsewhere.  Otherwise, you get
> into the case of people who don't enable it because they "know" their hardware
> doesn't have an EDAC ability, even if they *could* benefit from the function.
>
> On the other hand, if it's an EDAC-only thing, maybe under drivers/edac/$ARCH?

I don't see anything in the name of EDAC that implies hardware only...a 
software memory scrub could be considered "error detection and 
correction".  Might have to update the config help text though.

Chris

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