2011 IEEE/IFIP 41st International Conference on Dependable Systems &Amp; Networks (DSN) 2011
DOI: 10.1109/dsn.2011.5958244
|View full text |Cite
|
Sign up to set email alerts
|

Fault injection-based assessment of aspect-oriented implementation of fault tolerance

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2012
2012
2020
2020

Publication Types

Select...
3
2
2

Relationship

0
7

Authors

Journals

citations
Cited by 17 publications
(6 citation statements)
references
References 14 publications
0
6
0
Order By: Relevance
“…If the sequence silently diverges in the presence of faults, we record a silent data corruption. 2 The application state (task stacks) is checked for integrity at each checkpoint. To evaluate the fault containment within the kernel execution, we further recorded an SDC in case of violated integrity.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…If the sequence silently diverges in the presence of faults, we record a silent data corruption. 2 The application state (task stacks) is checked for integrity at each checkpoint. To evaluate the fault containment within the kernel execution, we further recorded an SDC in case of violated integrity.…”
Section: Discussionmentioning
confidence: 99%
“…Our work differs in that we use the generalpurpose AspectC++ compiler that allows us to focus on the implementation of software-based EDM/ERMs in the OS/application layer, instead of implementing special-purpose compilers. AOP also allows to separate the "business logic" from fault-tolerance implementations, which has, e.g., been pioneered by Alexandersson et al [2]-however at the cost of 300% runtime overhead.…”
Section: Software-based Soft-error Detection and Correctionmentioning
confidence: 99%
“…This modularity problem is attacked by exercising aspect-oriented programming with AspectC++ in [43], [44], [45]. For example, Alexandersson et al [45] implemented triple-time-redundant execution and control-flow checking as a proof of concept, which led to 300 % runtime overhead.…”
Section: Related Workmentioning
confidence: 99%
“…Authors in [8] proposed a fault injection study that estimates the fault coverage of two software implemented with AOP. They investigated the Double Signature Control Flow Checking (DSCFC) and the Triple Time Redundant Execution with Forward Recovery (TTRFR) mechanisms.…”
Section: Fault Tolerance Using Aopmentioning
confidence: 99%