A Comparison of Inject-on-Read and Inject-on-Write in ISA-Level Fault Injection

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

doi:10.1109/edcc.2015.24

Cited by 12 publications

(14 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In other words, all faults targeting a specific bit of a given register or memory word, from the time the register or the memory word is written into until it is read, are considered equivalent. Note that in order to obtain an accurate estimation of different dependability measures, it would be necessary to apply a weight factor corresponding to the number of faults in each equivalence class, as also addressed in previous works [20] [23] [27]. Inject-on-read corrupts the content of the source register (or memory word) of a machine instruction, emulating soft errors that occur in a data-item during the time it resides in an ISA register or a memory word.…”

Section: Goofi-2 Fault Injection Toolmentioning

confidence: 99%

“…The new features added were all lessons learned from developing and using GOOFI-2 in the past few years [20] …”

Section: Goofi-2 Fault Injection Toolmentioning

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-items targeted. For example, injecting faults in address data-items are more likely to raise a hardware exception mechanism, thus resulting in a program crash, compared to faults injected in data variables.…”

Section: Improving Controllabilitymentioning

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%

“…The current version of GOOFI-2 is also equipped with another ISA-level fault injection technique known as injecton-write [20], where using this techniques, we could also inject faults into the destination register or memory word of an instruction. The inject-on-write is well suited for emulating errors that propagate into a register or a memory word as a result of particle strikes in hardware resources within microprocessor such as ALUs, caches and internal pipeline registers.…”

Section: Goofi-2 Fault Injection Toolmentioning

confidence: 99%

See 4 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: Goofi-2 Fault Injection Toolmentioning

confidence: 99%

“…The new features added were all lessons learned from developing and using GOOFI-2 in the past few years [20] …”

Section: Goofi-2 Fault Injection Toolmentioning

confidence: 99%

Section: Improving Controllabilitymentioning

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%

Section: Goofi-2 Fault Injection Toolmentioning

confidence: 99%

See 3 more Smart Citations