Cited by 182Software Testing and Debugging TechniquesDistributed systems and fault toleranceRadiation Effects in Electronics

The DOI matches its Crossref record; 32 of the 32 references it cites were found in a registry or an index.

Quantifying the Accuracy of High-Level Fault Injection Techniques for Hardware Faults

Wei, Jiesheng, Thomas, Anna, Li, Guanpeng, Pattabiraman, Karthik·2014·2014 44th Annual IEEE/IFIP International Conference on Dependable Systems and Networks

Abstract

Hardware errors are on the rise with reducing feature sizes, however tolerating them in hardware is expensive. Researchers have explored software-based techniques for building error resilient applications. Many of these techniques leverage application-specific resilience characteristics to keep overheads low. Understanding application-specific resilience characteristics requires software fault-injection mechanisms that are both accurate and capable of operating at a high-level of abstraction to allow developers to reason about error resilience. In this paper, we quantify the accuracy of high-level software fault injection mechanisms vis-à-vis those that operate at the assembly or machine code levels. To represent high-level injection mechanisms, we built a fault injector tool based on the LLVM compiler, called LLFI. LLFI performs fault injection at the LLVM intermediate code level of the application, which is close to the source code. We quantitatively evaluate the accuracy of LLFI with respect to assembly level fault injection, and understand the reasons for the differences.

Overview

Integrity signals

Registry

Crossref · 10.1109/dsn.2014.2

Cites

32 of 32 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • The occurrence of faults may cause an application to crash, hang, or terminate by producing an erroneous result without alert (Silent Data Corruption).

    “The occurrence of faults may cause the application: i) to crash or the operating system to raise an exception blocking the execution, ii) to hang leading to a non-termination, or iii) to terminate by producing an erroneous result, without any alert, a.k.a. Silent Data Corruption (SDC) [31].”

Citations

Cites

Flagged first, then by citations

Research works printed but not linked: 2

  1. woof, 1995, The splash2 programs: Characterization and methodological considerations, ISCA, 24
  2. maia, 2002, Xceptiontm-enhanced automated fault-injection environment, DSN, 547

Cited by

Sorted by citations

Metadata

Authors
Wei, J., Thomas, A., Li, G., & Pattabiraman, K.
Affiliations
University of British Columbia (CA)
Venue
2014 44th Annual IEEE/IFIP International Conference on Dependable Systems and Networks
Publisher
IEEE
Published
2014-06
Pages
375-382
ISSN
1530-0889 (ISSN-L)
OpenAlex
W1965936844
Cited by
182
References
32
Citations by year
2026: 2 · 2025: 9 · 2024: 15 · 2023: 19 · 2022: 16 · 2021: 20 · 2020: 19 · 2019: 22 · 2018: 18 · 2017: 13 · 2016: 17 · 2015: 10 · 2014: 2
FWCI
9.27
Type
conference paper
Language
en
Open access
closed
Locations
International Conference on Dependable Systems & Networks/Proceedings (publishedVersion)
Topics
  • Physical Sciences › Computer Science › Software › Software Testing and Debugging Techniques
  • Physical Sciences › Computer Science › Computer Networks and Communications › Distributed systems and fault tolerance
  • Physical Sciences › Engineering › Electrical and Electronic Engineering › Radiation Effects in Electronics
Keywords
software fault injection, hardware fault injection, error resilience, high-level abstraction, hardware errors, error-tolerant applications

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review