>> Not to be too blunt, but how often would you expect this to be the case?
>
>Not very.
>
>> I agree it's a risk, however an _extremely_ small one at best, and I'd
>> never take odds in Las Vegas on that problem occuring unless intentionally
>> triggered (in which case, the bet was fixed). :)
>
>Agreed. The alternative is to CRC check a block of 16bit code and drop back
>via the BIOS for writeout
Maybe you could hide the critical data in page(s) which would not
normally be mapped. That wouldn't save you from RAM errors, but would
save you from random overlays.
john alvord
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/