diff options
author | Paul E. McKenney <paulmck@kernel.org> | 2021-04-27 23:51:35 +0300 |
---|---|---|
committer | Paul E. McKenney <paulmck@kernel.org> | 2021-05-11 02:05:07 +0300 |
commit | 3d78668e5b50f1a28fdfd4293fc61b90eb10ba75 (patch) | |
tree | 6f9df7b88eb753a06ad80fcd5f81d11f3068496e /kernel/rcu/rcutorture.c | |
parent | c43d3b0083b4f2e9b14174a5857ab06cbca986df (diff) | |
download | linux-3d78668e5b50f1a28fdfd4293fc61b90eb10ba75.tar.xz |
torture: Don't cap remote runs by build-system number of CPUs
Currently, if a torture scenario requires more CPUs than are present
on the build system, kvm.sh and friends limit the CPUs available to
that scenario. This makes total sense when the build system and the
system running the scenarios are one and the same, but not so much when
remote systems might well have more CPUs.
This commit therefore introduces a --remote flag to kvm.sh that suppresses
this CPU-limiting behavior, and causes kvm-remote.sh to use this flag.
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Diffstat (limited to 'kernel/rcu/rcutorture.c')
0 files changed, 0 insertions, 0 deletions