This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Automatic Instruction-Level Software-Only Recovery
January/February 2007 (vol. 27 no. 1)
pp. 36-47
ASCII Text
x 
 
George A. Reis, Jonathan Chang, David I. August, "Automatic Instruction-Level Software-Only Recovery," IEEE Micro, vol. 27, no. 1, pp. 36-47, January/February, 2007.
 
 
BibTex
x
 
@article{ 10.1109/MM.2007.4,
author = {George A. Reis and Jonathan Chang and David I. August},
title = {Automatic Instruction-Level Software-Only Recovery},
journal ={IEEE Micro},
volume = {27},
number = {1},
issn = {0272-1732},
year = {2007},
pages = {36-47},
doi = {http://doi.ieeecomputersociety.org/10.1109/MM.2007.4},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Micro
TI - Automatic Instruction-Level Software-Only Recovery
IS - 1
SN - 0272-1732
SP36
EP47
EPD - 36-47
A1 - George A. Reis,
A1 - Jonathan Chang,
A1 - David I. August,
PY - 2007
KW - reliability
KW - fault tolerance
KW - software-only fault tolerance
KW - fault recovery
VL - 27
JA - IEEE Micro
ER -
 
George A. Reis, Princeton University
Jonathan Chang, Princeton University
David I. August, Princeton University
Software-only reliability techniques protect against transient faults without the overhead of hardware techniques. However, although existing low-level software-only fault-tolerance techniques detect faults, they offer no recovery assistance. This article describes three automatic, instruction-level, software-only recovery techniques representing different trade-offs between reliability and performance.
Index Terms:
reliability, fault tolerance, software-only fault tolerance, fault recovery
Citation:
George A. Reis, Jonathan Chang, David I. August, "Automatic Instruction-Level Software-Only Recovery," IEEE Micro, vol. 27, no. 1, pp. 36-47, Jan.-Feb. 2007, doi:10.1109/MM.2007.4
Usage of this product signifies your acceptance of the Terms of Use.