lkml.org 
[lkml]   [2017]   [Jan]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH tip/core/rcu 0/9] Torture-test changes for 4.11
On Sat, Jan 14, 2017 at 01:25:33AM -0800, Paul E. McKenney wrote:
> 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.

Reviewed-by: Josh Triplett <josh@joshtriplett.org>

\
 
 \ /
  Last update: 2017-01-14 22:14    [W:0.081 / U:0.020 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site