From 4d9abaa9f1fe795774adb521c11d5425684ac8cc Mon Sep 17 00:00:00 2001 From: Fabian Posch Date: Fri, 24 Jan 2025 11:26:20 +0100 Subject: [PATCH] add glitch to failure classes --- fault_injection_async25.tex | 1 + 1 file changed, 1 insertion(+) diff --git a/fault_injection_async25.tex b/fault_injection_async25.tex index 25a665d..26b2ab2 100644 --- a/fault_injection_async25.tex +++ b/fault_injection_async25.tex @@ -187,6 +187,7 @@ When a transient is injected into a node, and given it is not masked by either t \item The glitch acts as additional spacing between what is perceived as two data tokens, injecting an additional one into the pipeline. This would also result in a \emph{token count failure} (and potentially a \emph{value failure}) \item The glitch changes the value of a data line and thus creates a \emph{value failure} or, in a DI-coding, a potential \emph{coding failure} \item A non-recoverable state is reached in the circuit, resulting in a \emph{deadlock} + \item Additionally, a static-0 or static-1 hazard propagates to the edge of the design, we register it as a \emph{glitch} \end{itemize} These failure modes are in accordance with the potential states of a circuit from \cite{bainbridgeGlitchSensitivityDefense2009}; we thus reuse the same failure classification as already presented in \cite{behalExplainingFaultSensitivity2021}.