public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: josh@joshtriplett.org
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org,
	laijs@cn.fujitsu.com, dipankar@in.ibm.com,
	akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
	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: Re: [PATCH tip/core/rcu 2/3] rcutorture: Test both RCU-sched and RCU-bh for Tiny RCU
Date: Tue, 12 May 2015 17:59:29 -0700	[thread overview]
Message-ID: <20150513005929.GE14292@cloud> (raw)
In-Reply-To: <1431470953-4910-2-git-send-email-paulmck@linux.vnet.ibm.com>

On Tue, May 12, 2015 at 03:49:12PM -0700, Paul E. McKenney wrote:
> From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> 
> Reported-by: "Ahmed, Iftekhar" <ahmedi@onid.oregonstate.edu>
> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>

Could you elaborate a bit more on this patch (ideally in its commit
message)?  I see an addition of a command-line parameter to test rcu_bh;
is rcu-sched already tested elsewhere by some other config, or does this
parameter somehow enable testing both?

>  tools/testing/selftests/rcutorture/configs/rcu/TINY02.boot | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/tools/testing/selftests/rcutorture/configs/rcu/TINY02.boot b/tools/testing/selftests/rcutorture/configs/rcu/TINY02.boot
> index 0f0802730014..6c1a292a65fb 100644
> --- a/tools/testing/selftests/rcutorture/configs/rcu/TINY02.boot
> +++ b/tools/testing/selftests/rcutorture/configs/rcu/TINY02.boot
> @@ -1,2 +1,3 @@
>  rcupdate.rcu_self_test=1
>  rcupdate.rcu_self_test_bh=1
> +rcutorture.torture_type=rcu_bh
> -- 
> 1.8.1.5
> 

  reply	other threads:[~2015-05-13  0:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 22:48 [PATCH tip/core/rcu 0/3] Tiny RCU updates for 4.2 Paul E. McKenney
2015-05-12 22:49 ` [PATCH tip/core/rcu 1/3] rcu: Further shrink Tiny RCU by making empty functions static inlines Paul E. McKenney
2015-05-12 22:49   ` [PATCH tip/core/rcu 2/3] rcutorture: Test both RCU-sched and RCU-bh for Tiny RCU Paul E. McKenney
2015-05-13  0:59     ` josh [this message]
2015-05-13 13:03       ` Steven Rostedt
2015-05-13 13:07       ` Paul E. McKenney
2015-05-13 16:32         ` Josh Triplett
2015-05-12 22:49   ` [PATCH tip/core/rcu 3/3] rcu: Correctly handle non-empty Tiny RCU callback list with none ready Paul E. McKenney
2015-05-13  0:58     ` josh
2015-05-13 13:09       ` Paul E. McKenney
2015-05-13  0:57   ` [PATCH tip/core/rcu 1/3] rcu: Further shrink Tiny RCU by making empty functions static inlines josh
2015-05-13 12:59     ` 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=20150513005929.GE14292@cloud \
    --to=josh@joshtriplett.org \
    --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=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.com \
    --cc=paulmck@linux.vnet.ibm.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