summaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/utils.py
diff options
context:
space:
mode:
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>2018-07-13 22:09:14 +0300
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>2018-08-31 02:03:40 +0300
commitc116dba68d19246639e4fdb8c75756c67d6d268f (patch)
tree68afbe2d9a116d13b34f0da980e8fc3a8386e47d /scripts/gdb/linux/utils.py
parenta0ef9ec24144799b5b47fa54c38f9a0f9dfe9a59 (diff)
downloadlinux-c116dba68d19246639e4fdb8c75756c67d6d268f.tar.xz
rcutorture: Dump reader protection sequence if failures or close calls
Now that RCU can have readers with multiple segments, it is quite possible that a specific sequence of reader segments might result in an rcutorture failure (reader spans a full grace period as detected by one of the grace-period primitives) or an rcutorture close call (reader potentially spans a full grace period based on reading out the RCU implementation's grace-period counter, but with no ordering). In such cases, it would clearly ease debugging if the offending specific sequence was known. For the first reader encountering a failure or a close call, this commit therefore dumps out the segments, delay durations, and whether or not the reader was preempted. Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com> [ paulmck: Mark variables static, as suggested by kbuild test robot. ]
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions