summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorPaul E. McKenney <paulmck@kernel.org>2019-05-03 17:34:20 +0300
committerPaul E. McKenney <paulmck@kernel.org>2023-03-24 20:24:15 +0300
commit68f7bcab87eb47e7f9ca71ddca7fb976b92bc3a9 (patch)
treebb31a8a0f2f677b676432338c953d504bca822f7 /tools/perf/scripts/python/export-to-postgresql.py
parentdf0f675065bf003c4f182941f62b01b06be97182 (diff)
downloadlinux-68f7bcab87eb47e7f9ca71ddca7fb976b92bc3a9.tar.xz
tools/memory-model: Add data-race capabilities to judgelitmus.sh
This commit adds functionality to judgelitmus.sh to allow it to handle both the "DATARACE" markers in the "Result:" comments in litmus tests and the "Flag data-race" markers in LKMM output. For C-language tests, if either marker is present, the other must also be as well, at least for litmus tests having a "Result:" comment. If the LKMM output indicates a data race, then failures of the Always/Sometimes/Never portion of the "Result:" prediction are forgiven. The reason for forgiving "Result:" mispredictions is that data races can result in "interesting" compiler optimizations, so that all bets are off in the data-race case. [ paulmck: Apply Akira Yokosawa feedback. ] Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions