torture: Handle jitter for CPUs that cannot be offlined
authorPaul E. McKenney <paulmck@kernel.org>
Mon, 14 Oct 2019 14:05:38 +0000 (07:05 -0700)
committerPaul E. McKenney <paulmck@kernel.org>
Mon, 9 Dec 2019 21:00:26 +0000 (13:00 -0800)
commit517f17aed0ce678dfa82d7dd4e2593fc1bac799c
tree7bb1cc3814099ad36031bd2725d6b100118d1644
parent9aa55ec206a6841e297c9df7e737b3d57f048a82
torture: Handle jitter for CPUs that cannot be offlined

Currently, jitter.sh assumes that the underlying hypervisor will be
configured with all CPUs hotpluggable, with the possible exception
of CPU 0.  However, there are installations where the hypervisor
prohibits offlining, which breaks jitter.sh.  This commit therefore
lists the CPUs that cannot be offlined up front, and checks for the
case where no CPU can be offlined in the loop.

Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
tools/testing/selftests/rcutorture/bin/jitter.sh