A Study of the Impact of Single Bit-Flip and Double Bit-Flip Errors on Program Execution

Ayatolahi, Fatemeh; Sangchoolie, Behrooz; Johansson, Roger; Karlsson, Johan

doi:10.1007/978-3-642-40793-2_24

Cited by 35 publications

(22 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This technique leverage the fact that faults in certain bits in the program counter and the stack pointer are always detected by machine exceptions [21]. We show that exclusion of these bits from the fault space could significantly reduce the time it takes to conduct a fault injection campaign.…”

Section: Improving Efficiencymentioning

confidence: 99%

“…The motivation for the data type identification comes from prior work [20] [21] [22] where we learned that the outcome of a fault injection experiment is highly dependent on the type of data-item targeted. Here data-item refers to the content of a register or memory word, which could be a data variable, memory address, or control information.…”

Section: Data Type Identificationmentioning

confidence: 99%

“…However, ideally, the fault model should account for both single and multiple bit errors. There has been a number of studies [21] [31] comparing the commonly used single bit-flip model with the double bit-flip model, as one variation of multiple bit-flip model. Results of these studies show that the percentage of SDCs in the output of the programs under study, is marginally different for the two fault models.…”

Section: Data Type Identificationmentioning

confidence: 99%

See 2 more Smart Citations

Light-Weight Techniques for Improving the Controllability and Efficiency of ISA-Level Fault Injection Tools

Sangchoolie

Johansson

Karlsson

2017

2017 IEEE 22nd Pacific Rim International Symposium on Dependable Computing (PRDC)

Self Cite

View full text Add to dashboard Cite

Abstract-ISA-level fault injection, i.e. the injection of bitflip faults in Instruction Set Architecture (ISA) registers and main memory words, is widely used for studying the impact of transient and intermittent hardware faults. ISA-level fault injection tools can be characterized by different properties such as repeatability, observability, reachability, intrusiveness, efficiency and controllability. This paper presents two preinjection analysis techniques that improve controllability and efficiency using object code analysis. To improve controllability, we propose a technique for identifying the type of data that is stored in a potential target location. This allows the user to selectively direct fault injections to addresses, data and/or control information. Experimental results show that the data type of 84-100% of the targets locations in 8 programs were successfully identified by this technique. The second technique improves efficiency by fault pruning, i.e., by avoiding injection of faults that is known a priori to be detected by the tested system. This technique leverage the fact that faults in certain bits in the program counter and the stack pointer are always detected by machine exceptions. We show that exclusion of these bits from the fault space could significantly prune the fault space and reduce the time it takes to conduct a fault injection campaign.

show abstract

Section: Improving Efficiencymentioning

confidence: 99%

Section: Data Type Identificationmentioning

confidence: 99%

Section: Data Type Identificationmentioning

confidence: 99%

See 1 more Smart Citation

Light-Weight Techniques for Improving the Controllability and Efficiency of ISA-Level Fault Injection Tools

Sangchoolie

Johansson

Karlsson

2017

2017 IEEE 22nd Pacific Rim International Symposium on Dependable Computing (PRDC)

Self Cite

View full text Add to dashboard Cite

show abstract

“…[11], [12], [13], [14]. FI has recently received renewed attention in the automotive domain since the settlement of ISO 26262, and for faultinjection benchmarking of embedded systems [2], [15].…”

Section: Related Workmentioning

confidence: 99%

“…This standard has pushed recommendations towards different methods and techniques that should be adopted in a development process to assure that "no unreasonable risk is due to hazards caused by malfunctioning behavior of electrical and electronic systems". In particular, ISO 26262 highly recommends fault injection (FI) as a technique to verify and validate electrical and electronic systems, throughout the whole development process, including the early design phase [2,3]. It is worth to mention that, even though experimental validation of embedded systems is of common practice in industry, fault injection adoption in the early design phase, as advocated by the ISO26262 standard, is not common and unclear.…”

Section: Introductionmentioning

confidence: 99%

From Safety Analyses to Experimental Validation of Automotive Embedded Systems

Pintard

Fabre

Leeman

et al. 2014

2014 IEEE 20th Pacific Rim International Symposium on Dependable Computing

View full text Add to dashboard Cite

Abstract-Automotive embedded systems are becoming increasingly complex. Therefore verification activities are paramount to ensure safety. ISO 26262 is the first standard specifically dedicated to automotive safety systems. This standard requires introducing fault injection (FI) from the very early phases of the development process. Our work aims at developing an approach that will help integrate FI in the whole development process in a continuous way, from system requirements to the verification and validation phase. In this paper, we concentrate on exploring the benefits of safety analyses for experimental validation of the system. We propose an analogy between FI during the pre-implementation phase with safety analyses that are of common use during system design. We finally illustrate this approach on a case study from the automotive domain.

show abstract