rcutorture: Decorate failing reader segments with CPU ID
authorPaul E. McKenney <paulmck@kernel.org>
Wed, 16 Oct 2024 16:50:40 +0000 (09:50 -0700)
committerUladzislau Rezki (Sony) <urezki@gmail.com>
Sat, 14 Dec 2024 16:02:11 +0000 (17:02 +0100)
commit579a05da40a4980870a13d30cd0532f77aa15b8b
tree5f18f6d61fb4d8a085516c2d68d6d33815fc7d9b
parent5ec090011bd2bb6ea6c2c607371db57ee0506a89
rcutorture: Decorate failing reader segments with CPU ID

This commit adds CPU number to the "Failure/close-call rcutorture reader
segments" list printed at the end of an rcutorture run that had too-short
grace periods.  This information can help debugging interactions with
migration and CPU hotplug.

However, experience indicates that sampling the CPU number in rcutorture's
read-side code can reduce the probability of too-short bugs by a small
integer factor.  And small integer factors are crucial to RCU bug hunting,
so this commit also introduces a default-off RCU_TORTURE_TEST_LOG_CPU
Kconfig option to enable this CPU-number-logging functionality at
build time.

Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
kernel/rcu/Kconfig.debug
kernel/rcu/rcutorture.c