Hardware Approach for Detecting, Exposing and Tolerating High Level Atomicity Violations

Research output: Other contribution


In this paper we address a solution for detecting and tolerating one of the most typical concurrency bugs: atomicity violations. More specifically, we address High-Level Atomicity Violations (HLAV). High-level atomicity violations result from the misspecification of the scope of an atomic block, by splitting it in two or more atomic blocks which may be interleaved with other atomic blocks. Figure 1 shows an example of this type of atomicity violation. The intuitive idea behind HLAV is that if two shared data items (e.g., memory locations) were both accessed inside an atomic block, they are interrelated and probably the programmer intention is that there shall be no interleavings between these two accesses. Therefore, if (in the same program) this two addresses are accessed separately in different atomic blocks, an unfortunate interleaving may cause an atomicity violation.
Original languageEnglish
Place of PublicationVienna, Austria
Publication statusPublished - 2014


Dive into the research topics of 'Hardware Approach for Detecting, Exposing and Tolerating High Level Atomicity Violations'. Together they form a unique fingerprint.

Cite this