torture: Handle jitter for CPUs that cannot be offlined

Browse source

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>

...

This commit is contained in:

Paul E. McKenney 2019-10-14 07:05:38 -07:00

parent 9aa55ec206

commit 517f17aed0

1 changed files with 20 additions and 6 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

26

tools/testing/selftests/rcutorture/bin/jitter.sh

View file