From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, jiangshanlai@gmail.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org,
rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
dvhart@linux.intel.com, fweisbec@gmail.com, oleg@redhat.com,
bobby.prani@gmail.com
Subject: [PATCH tip/core/rcu 0/9] Torture-test changes for 4.11
Date: Sat, 14 Jan 2017 01:25:33 -0800 [thread overview]
Message-ID: <20170114092533.GA23650@linux.vnet.ibm.com> (raw)
Hello!
This series provides torture-test updates:
1. Add a check for CONFIG_RCU_STALL_COMMON for TINY01, in order
to complain if this case is not tested.
2. Add CONFIG_PROVE_RCU_REPEATEDLY=y for TINY02, in order to test
this case.
3. Add tests without slow grace period setup/cleanup, as this case
is what is actually used in production.
4. Run at least one test with CONFIG_DEBUG_OBJECTS_RCU_HEAD, to make
sure that this case is tested regularly.
5. Run one test with DEBUG_LOCK_ALLOC but not PROVE_LOCKING, to make
sure that this case is tested regularly.
6. Run a couple scenarios with CONFIG_RCU_EQS_DEBUG, again to make
sure that this case is tested regularly.
7. Update RCU test scenario documentation.
8. Fix potential memory leak with rw lock test, courtesy of Yang Shi.
9. Enable DEBUG_OBJECTS_RCU_HEAD for Tiny RCU, you guessed it, to
make sure that this case is regularly tested.
Thanx, Paul
------------------------------------------------------------------------
kernel/locking/locktorture.c | 6 ++
tools/testing/selftests/rcutorture/configs/rcu/CFcommon | 3 -
tools/testing/selftests/rcutorture/configs/rcu/TINY01 | 1
tools/testing/selftests/rcutorture/configs/rcu/TINY02 | 3 -
tools/testing/selftests/rcutorture/configs/rcu/TREE01 | 3 +
tools/testing/selftests/rcutorture/configs/rcu/TREE02 | 4 +
tools/testing/selftests/rcutorture/configs/rcu/TREE03 | 3 +
tools/testing/selftests/rcutorture/configs/rcu/TREE04 | 4 +
tools/testing/selftests/rcutorture/configs/rcu/TREE05 | 3 +
tools/testing/selftests/rcutorture/configs/rcu/TREE06 | 3 +
tools/testing/selftests/rcutorture/configs/rcu/TREE07 | 3 +
tools/testing/selftests/rcutorture/configs/rcu/TREE08 | 4 -
tools/testing/selftests/rcutorture/doc/TREE_RCU-kconfig.txt | 33 +++++++++++-
13 files changed, 65 insertions(+), 8 deletions(-)
next reply other threads:[~2017-01-14 9:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 9:25 Paul E. McKenney [this message]
2017-01-14 9:25 ` [PATCH tip/core/rcu 1/9] torture: Add a check for CONFIG_RCU_STALL_COMMON for TINY01 Paul E. McKenney
2017-01-14 9:25 ` [PATCH tip/core/rcu 2/9] torture: Add CONFIG_PROVE_RCU_REPEATEDLY=y for TINY02 Paul E. McKenney
2017-01-14 9:25 ` [PATCH tip/core/rcu 3/9] torture: Add tests without slow grace period setup/cleanup Paul E. McKenney
2017-01-14 9:25 ` [PATCH tip/core/rcu 4/9] torture: Run at least one test with CONFIG_DEBUG_OBJECTS_RCU_HEAD Paul E. McKenney
2017-01-14 9:25 ` [PATCH tip/core/rcu 5/9] torture: Run one test with DEBUG_LOCK_ALLOC but not PROVE_LOCKING Paul E. McKenney
2017-01-14 9:25 ` [PATCH tip/core/rcu 6/9] torture: Run a couple scenarios with CONFIG_RCU_EQS_DEBUG Paul E. McKenney
2017-01-14 9:25 ` [PATCH tip/core/rcu 7/9] torture: Update RCU test scenario documentation Paul E. McKenney
2017-01-14 9:25 ` [PATCH tip/core/rcu 8/9] locktorture: Fix potential memory leak with rw lock test Paul E. McKenney
2017-01-14 9:25 ` [PATCH tip/core/rcu 9/9] torture: Enable DEBUG_OBJECTS_RCU_HEAD for Tiny RCU Paul E. McKenney
2017-01-14 21:13 ` [PATCH tip/core/rcu 0/9] Torture-test changes for 4.11 Josh Triplett
2017-01-15 5:39 ` Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170114092533.GA23650@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhart@linux.intel.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).