@bcantrill I'm sure many at oxide would find this quite interesting (if one can overcome the ecache traumas :P)
"Injecting Errors for Fun and Profit"
"Error-detection and correction features are only as good as our ability to test them."
@bcantrill I'm sure many at oxide would find this quite interesting (if one can overcome the ecache traumas :P)
"Injecting Errors for Fun and Profit"
"Error-detection and correction features are only as good as our ability to test them."
@bcantrill Of particular note:
"Since the e-cache parity crisis, error injection has become a core competency of what is now Oracle's Systems organization. As new processors and their supporting ASICs are designed, error and diagnostic reviews make sure they have the appropriate ability to inject errors into their internal structures, and the error injector is enhanced to inject those errors so that we can test our error handling, diagnosis, and containment software in an end-to-end fashion."
@bcantrill "Of course, companies such as IBM and Oracle that control both the hardware they sell and the software that supports it are best positioned to take advantage of error injection technology to improve the handling, diagnosis, and containment of errors by their respective systems, as having the hardware and software people all in a single organization allows the necessary continuous interaction between them as new hardware and software is developed."
@bcantrill "When hardware and software development is divided among different organizations, as it is in the Windows, VMware, and Linux worlds (or, alternatively, the Intel and AMD worlds), exploiting error injection technology for product improvement is much more difficult."
@developing_agent Yes, I commissioned that article from Steve when I was on the ACM Queue board. 😉