Re: marching through all physical memory in software

Valdis.Kletnieks
2009-02-02T22:46:19Z

[-- Attachment #1: Type: text/plain, Size: 739 bytes --]

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?

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]