Reorder chapters + put abstract into frontmatter
This commit is contained in:
@@ -40,7 +40,8 @@ The effects of injected faults are later evaluated through the readouts describe
|
||||
|
||||
Instead of injecting a single-bit fault at every possible location derived from the \gls{goldenrun}, the fault space is pruned before the campaign is run.
|
||||
Equivalence classes of faults leading to the same outcome are identified and represented by a single \gls{pilot} experiment, so the outcomes of all experiments that belong to an equivalence class can be determined by performing injections on only its \gls{pilot}.
|
||||
Because injections into different bits can cause different outcomes, only injections into the same bit can belong to a single equivalence class, additionally, there must not be intervening accesses into a memory location within a single equivalence class.
|
||||
Because injections into different bits can cause different outcomes, only injections into the same bit can belong to a single equivalence class.
|
||||
Additionally, there must not be intervening accesses into a memory location within a single equivalence class.
|
||||
|
||||
For example, if a single byte at the memory location \(m\) is written by the program under test at time \(t_{0}\) and read back (without \(m\) being accessed in between) at time \(t_{1}\) with \(t_{1} > t_{0}\), each injection into bit \(b\) of \(m\) during the time interval \([t_{0}, t_{1}]\) would cause the same outcome (multiple simultaneous faults are outside the scope of this thesis).
|
||||
Instead of performing \(t_{1} - t_{0} + 1\) individual injections into bit \(b\) of \(m\), the pruner marks \([t_{0}, t_{1}]\) as an equivalence class, represented by a single injection into bit \(b\) of \(m\) at time \(t_{1}\) (or any other \(t\in [t_{0}, t_{1}]\)).
|
||||
@@ -97,6 +98,6 @@ where \(\mathbf{1}\{o_{c,b} = o\}\) is the indicator function, which equals one
|
||||
\todo[inline]{Don't put this in a footnote, put it in controlling what data gets extracted from the experiments}
|
||||
|
||||
Weighted outcome totals are reported separately for each fault category, execution mode and injection location (memory, registers or instruction-pointer).
|
||||
Outcome shares describe the composition of each variant's fault space, while absolute totals show differences in vulnerability caused by executaion duration and memory footprint.
|
||||
Outcome shares describe the composition of each variant's fault space, while absolute totals show differences in vulnerability caused by execution duration and memory footprint.
|
||||
|
||||
\end{document}
|
||||
|
||||
Reference in New Issue
Block a user