lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 06 Feb 2009 10:00:30 +0100 From: Andi Kleen <andi@...stfloor.org> To: "Chris Friesen" <cfriesen@...tel.com> Cc: linux-kernel@...r.kernel.org Subject: Re: marching through all physical memory in software "Chris Friesen" <cfriesen@...tel.com> writes: > Someone is asking me about the feasability of "scrubbing" system > memory by accessing each page and handling the ECC faults. I would expect any ECC RAM capable memory controller designed in the last 10-15 years to be able to do this on its own without software intervention. Is that not true? It is certainly on x86 (although you sometimes have to change BIOS options) -Andi -- ak@...ux.intel.com -- Speaking for myself only. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/