diff options
| author |   Paul E. McKenney <paulmck@kernel.org> | 2024-10-16 09:50:40 -0700 |
|---|---|---|
| committer |   Uladzislau Rezki (Sony) <urezki@gmail.com> | 2024-12-14 17:02:11 +0100 |
| commit | 579a05da40a4980870a13d30cd0532f77aa15b8b (patch) | |
| tree | 5f18f6d61fb4d8a085516c2d68d6d33815fc7d9b /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | rcutorture: Make the TREE03 scenario do preemption (diff) | |
| download | wireguard-linux-579a05da40a4980870a13d30cd0532f77aa15b8b.tar.xz wireguard-linux-579a05da40a4980870a13d30cd0532f77aa15b8b.zip | |
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>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions