The DOI matches its Crossref record.
Eliminating microarchitectural dependency from Architectural Vulnerability
Abstract
The architectural vulnerability factor (AVF) of a hardware structure is the probability that a fault in the structure will affect the output of a program. AVF captures both microarchitectural and architectural fault masking effects; therefore, AVF measurements cannot generate insight into the vulnerability of software independent of hardware. To evaluate the behavior of software in the presence of hardware faults, we must isolate the software-dependent (architecture-level masking) portion of AVF from the hardware-dependent (microarchitecture-level masking) portion, providing a quantitative basis to make reliability decisions about software independent of hardware. In this work, we demonstrate that the new program vulnerability factor (PVF) metric provides such a basis: PVF captures the architecture-level fault masking inherent in a program, allowing software designers to make quantitative statements about a program's tolerance to soft errors. PVF can also explain the AVF behavior of a program when executed on hardware; PVF captures the workload-driven changes in AVF for all structures. Finally, we demonstrate two practical uses for PVF: choosing algorithms and compiler optimizations to reduce a program's failure rate.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cited by
SASSIFI: An architecture-level fault injection tool for GPU application resilience evaluation
Hari, S. K. S., Tsai, T., Stephenson, M., Keckler, S. W., & Emer, J. (2017) · 2017 IEEE International Symposium on Performance Analysis of Systems and Software (ISPASS) · doi:10.1109/ispass.2017.7975296 · Cited by 181
GPU-Qin: A methodology for evaluating the error resilience of GPGPU applications
Fang, B., Pattabiraman, K., Ripeanu, M., & Gurumurthi, S. (2014) · 2014 IEEE International Symposium on Performance Analysis of Systems and Software (ISPASS) · doi:10.1109/ispass.2014.6844486 · Cited by 142
Rech, P. (2024) · IEEE Transactions on Nuclear Science · doi:10.1109/tns.2024.3349956 · Cited by 75
Demystifying the System Vulnerability Stack: Transient Fault Effects Across the Layers
Papadimitriou, G., & Gizopoulos, D. (2021) · 2021 ACM/IEEE 48th Annual International Symposium on Computer Architecture (ISCA) · doi:10.1109/isca52012.2021.00075 · Cited by 74
Cross-Layer Reliability Evaluation and Efficient Hardening of Large Vision Transformers Models
Roquet, L., Fernandes dos Santos, F., Rech, P., Traiola, M., Sentieys, O., & Kritikakou, A. (2024) · Proceedings of the 61st ACM/IEEE Design Automation Conference · doi:10.1145/3649329.3655688 · Cited by 16
“The PVF is the probability of an injected fault propagating from the assembly instruction to the application output [21].”
Metadata
- Authors
- Sridharan, V., & Kaeli, D. R.
- Venue
- 2009 IEEE 15th International Symposium on High Performance Computer Architecture
- Publisher
- IEEE
- Published
- 2009-02
- Pages
- 117-128
- ISSN
- 1530-0897 (ISSN-L)
- OpenAlex
- W2123907700
- Cited by
- 182
- References
- 0
- FWCI
- 12.96
- Type
- conference paper
- Language
- en
- Open access
- closed
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
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Eliminating microarchitectural dependency from Architectural Vulnerability. https://app.cochat.ai/papers/10.1109/hpca.2009.4798243
- The paper
- Sridharan, V., & Kaeli, D. R. (2009). Eliminating microarchitectural dependency from Architectural Vulnerability. 2009 IEEE 15th International Symposium on High Performance Computer Architecture. https://doi.org/10.1109/hpca.2009.4798243
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.