rcutorture: Correctly handle CONFIG_RCU_TORTURE_TEST_* options
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Mon, 10 Apr 2017 23:15:06 +0000 (16:15 -0700)
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Thu, 8 Jun 2017 15:25:22 +0000 (08:25 -0700)
commit39687d6c1dc0c842ede1d4b4677931170c51305d
tree3915a8b6bd94324c2fac2c882f69cef33d93deb3
parentf92c734f02cbf10e40569facff82059ae9b61920
rcutorture: Correctly handle CONFIG_RCU_TORTURE_TEST_* options

The rcutorture scripting handles the CONFIG_*_TORTURE_TEST Kconfig
options specially, and therefore greps them out of the Kconfig-fragment
files.  Unfortunately, a poor choice of grep pattern means that the
CONFIG_RCU_TORTURE_TEST_SLOW_CLEANUP, CONFIG_RCU_TORTURE_TEST_SLOW_INIT,
and CONFIG_RCU_TORTURE_TEST_SLOW_PREINIT Kconfig options are also grepped
out, preventing rcutorture from using them.  This commit therefore fixes
the offending grep pattern to focus only on the CONFIG_*_TORTURE_TEST
Kconfig options.

Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
tools/testing/selftests/rcutorture/bin/kvm-build.sh