rcutorture: Make scripts analyze rcuperf trace data, if present
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Sun, 31 Jan 2016 00:51:36 +0000 (16:51 -0800)
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Thu, 31 Mar 2016 20:38:57 +0000 (13:38 -0700)
commit2b03d038457fc8d694d34981cb0a2f1702ba35d6
tree801cf48041b05e7c275fff70f124f1cbbfa11c37
parentac2bb275e8e5abddb0815ff2b7aa383ed6d007a4
rcutorture: Make scripts analyze rcuperf trace data, if present

The rcuperf event-trace data is more accurate than are the rcuperf
printk()s because locking keeps things ordered.  This commit therefore
parses and analyzes this event-trace data if present, and falls back on
the printk()s otherwise.

Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
tools/testing/selftests/rcutorture/bin/kvm-recheck-rcuperf-ftrace.sh [new file with mode: 0755]
tools/testing/selftests/rcutorture/bin/kvm-recheck-rcuperf.sh