diff options
author | 2021-12-17 12:33:53 -0800 | |
---|---|---|
committer | 2022-02-01 17:24:38 -0800 | |
commit | e22ef8df415d924428e35c9c112526306e684adc (patch) | |
tree | 5eb2f1dd48b8eb0cea56e803ce0735e9c5eda022 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | rcutorture: Increase visibility of forward-progress hangs (diff) | |
download | wireguard-linux-e22ef8df415d924428e35c9c112526306e684adc.tar.xz wireguard-linux-e22ef8df415d924428e35c9c112526306e684adc.zip |
rcutorture: Make rcu_fwd_cb_nodelay be a counter
Back when only one rcutorture kthread could do forward-progress testing,
it was just fine for rcu_fwd_cb_nodelay to be a non-atomic bool. It was
set at the start of forward-progress testing and cleared at the end.
But now that there are multiple threads, the value can be cleared while
one of the threads is still doing forward-progress testing. This commit
therefore makes rcu_fwd_cb_nodelay be an atomic counter, replacing the
WRITE_ONCE() operations with atomic_inc() and atomic_dec().
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