data-aggregator: document "onwrite" fault model requirements

The *-onwrite.sh analysis scripts only work if import-trace was not
run with --no-write-ecs, i.e. they only work if writing memory
accesses were imported into the "trace" table.

Change-Id: Icb2ea4e72d2200c886d4f9074f2da0f9bfd6ac85
This commit is contained in:
Horst Schirmeier
2018-06-22 19:57:12 +02:00
parent 3abdc51043
commit 0baca64468
6 changed files with 16 additions and 0 deletions

View File

@ -8,6 +8,9 @@ corrupted, and completely disregards storage duration (e.g. time between write
and subsequent read). The metric is calculated from the results of a normal
"inject-on-read" campaign, only using the FI results from memory accesses that
directly follow a "write" access.
Only works if write equivalence classes are also imported into the database
(i.e. import-trace is not run with --no-write-ecs).
EOT
}
MUST_FILTER=1