Hi Paul, Please find v2 of the RCU early boot tests. For now all we do in these tests are enqueue test callbacks and check if they are being invoked or not.
I was able to reproduce the hang which Amit reported after reverting the fix. So this should catch such errors if they occur in the future. I enabled the selftests in a few rcutorture configurations. Thanks! -- Pranith v2: removed srcu tests and updated according to feedback Pranith Kumar (3): rcu: Add early boot self tests doc: Document RCU self test boot params rcutorture: Enable RCU self test in configs Documentation/kernel-parameters.txt | 9 +++ kernel/rcu/rcu.h | 2 + kernel/rcu/tiny.c | 4 +- kernel/rcu/tree.c | 2 + kernel/rcu/update.c | 82 ++++++++++++++++++++++ .../selftests/rcutorture/configs/rcu/TINY02 | 2 + .../selftests/rcutorture/configs/rcu/TINY02.boot | 2 + .../selftests/rcutorture/configs/rcu/TREE05.boot | 1 + .../selftests/rcutorture/configs/rcu/TREE06.boot | 3 + .../selftests/rcutorture/configs/rcu/TREE08 | 2 + .../selftests/rcutorture/configs/rcu/TREE08.boot | 2 + 11 files changed, 110 insertions(+), 1 deletion(-) create mode 100644 tools/testing/selftests/rcutorture/configs/rcu/TINY02.boot create mode 100644 tools/testing/selftests/rcutorture/configs/rcu/TREE06.boot -- 2.1.0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
