Messages in this thread | | | Date | Tue, 3 Feb 2009 23:25:01 +0100 | From | Pavel Machek <> | Subject | Re: marching through all physical memory in software |
| |
Hi!
>>> 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.
Software memory scrub would no longer be a "driver" :-). So it should go into kernel/scrub or mm/scrub or maybe mm/edac or something.
-- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
| |