a0e6ddd519
For the eCos kernel test campaign we define a relatively "special" metric to compare FI results from different applications: Instead of aligning the fault-space dimensions (e.g., by artificially adding "don't care" space to the right for shorter application variants), we only keep the data address axis constant. The rationale behind this is that -- despite the benchmark applications' run-to-completion behavior -- an operating system's scheduler usually runs ad infinitum, and that we therefore can extrapolate from a short application run to any longer period. In essence, this means we use a failure/experiment-length quotient (ignoring the Y axis for simplicity, as it is constant in size) to compare application variants, instead of an absolute failure count. One important side effect is that we do not punish any application slowdown with this metric. (And simply prolongating non-susceptible program sections with, e.g., NOPs, seemingly "improves" fault tolerance.) git-svn-id: https://www4.informatik.uni-erlangen.de/i4svn/danceos/trunk/devel/fail@1922 8c4709b5-6ec9-48aa-a5cd-a96041d1645a