public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Joel Fernandes <joelaf@google.com>
Cc: linux-kernel@vger.kernel.org, kernel-team@android.com,
	"Joel Fernandes (Google)" <joel@joelfernandes.org>,
	Josh Triplett <josh@joshtriplett.org>,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	mingo@redhat.com, Steven Rostedt <rostedt@goodmis.org>,
	tglx@linutronix.de
Subject: Re: [PATCH 1/2] rcutorture: Disable RT throttling for boost tests
Date: Mon, 11 Jun 2018 05:56:58 -0700	[thread overview]
Message-ID: <20180611125658.GR3593@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180610234544.150933-1-joel@joelfernandes.org>

On Sun, Jun 10, 2018 at 04:45:43PM -0700, Joel Fernandes wrote:
> From: "Joel Fernandes (Google)" <joel@joelfernandes.org>
> 
> Currently rcutorture is not able to torture RCU boosting properly. This
> is because the rcutorture's boost threads which are doing the torturing
> may be throttled due to RT throttling.
> 
> This patch makes rcutorture use the right torture technique (unthrottled
> rcutorture boost tasks) for torturing RCU so that the test fails
> correctly when no boost is available.
> 
> Currently this requires accessing sysctl_sched_rt_runtime directly, but
> that should be Ok since rcutorture is test code. Such direct access is
> also only possible if rcutorture is used as a built-in so make it
> conditional on that.
> 
> Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org>

Thank you, Joel!  I have queued these for testing and review.
Peter Zijlstra might have some feedback on variable access, but will
test first.

							Thanx, Paul

> ---
>  kernel/rcu/rcutorture.c | 29 +++++++++++++++++++++++++++++
>  1 file changed, 29 insertions(+)
> 
> diff --git a/kernel/rcu/rcutorture.c b/kernel/rcu/rcutorture.c
> index 5219e7ccd8a4..00e06349d7bb 100644
> --- a/kernel/rcu/rcutorture.c
> +++ b/kernel/rcu/rcutorture.c
> @@ -55,6 +55,7 @@
>  #include <linux/torture.h>
>  #include <linux/vmalloc.h>
>  #include <linux/sched/debug.h>
> +#include <linux/sched/sysctl.h>
> 
>  #include "rcu.h"
> 
> @@ -772,6 +773,32 @@ static void rcu_torture_boost_cb(struct rcu_head *head)
>  	smp_store_release(&rbip->inflight, 0);
>  }
> 
> +static int old_rt_runtime = -1;
> +
> +static void rcu_torture_disable_rt_throttle(void)
> +{
> +	/*
> +	 * Disable RT throttling so that rcutorture's boost threads don't get
> +	 * throttled. Only possible if rcutorture is built-in otherwise the
> +	 * user should manually do this by setting the sched_rt_period_us and
> +	 * sched_rt_runtime sysctls.
> +	 */
> +	if (!IS_BUILTIN(CONFIG_RCU_TORTURE_TEST) || old_rt_runtime != -1)
> +		return;
> +
> +	old_rt_runtime = sysctl_sched_rt_runtime;
> +	sysctl_sched_rt_runtime = -1;
> +}
> +
> +static void rcu_torture_enable_rt_throttle(void)
> +{
> +	if (!IS_BUILTIN(CONFIG_RCU_TORTURE_TEST) || old_rt_runtime == -1)
> +		return;
> +
> +	sysctl_sched_rt_runtime = old_rt_runtime;
> +	old_rt_runtime = -1;
> +}
> +
>  static int rcu_torture_boost(void *arg)
>  {
>  	unsigned long call_rcu_time;
> @@ -1510,6 +1537,7 @@ static int rcutorture_booster_cleanup(unsigned int cpu)
>  	mutex_lock(&boost_mutex);
>  	t = boost_tasks[cpu];
>  	boost_tasks[cpu] = NULL;
> +	rcu_torture_enable_rt_throttle();
>  	mutex_unlock(&boost_mutex);
> 
>  	/* This must be outside of the mutex, otherwise deadlock! */
> @@ -1526,6 +1554,7 @@ static int rcutorture_booster_init(unsigned int cpu)
> 
>  	/* Don't allow time recalculation while creating a new task. */
>  	mutex_lock(&boost_mutex);
> +	rcu_torture_disable_rt_throttle();
>  	VERBOSE_TOROUT_STRING("Creating rcu_torture_boost task");
>  	boost_tasks[cpu] = kthread_create_on_node(rcu_torture_boost, NULL,
>  						  cpu_to_node(cpu),
> -- 
> 2.18.0.rc1.242.g61856ae69a-goog
> 

      parent reply	other threads:[~2018-06-11 15:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-10 23:45 [PATCH 1/2] rcutorture: Disable RT throttling for boost tests Joel Fernandes
2018-06-10 23:45 ` [PATCH 2/2] rcutorture: Make boost test more robust Joel Fernandes
2018-06-13  6:57   ` [lkp-robot] [rcutorture] 46e26223e3: WARNING:at_kernel/rcu/rcutorture.c:#rcu_torture_stats_print kernel test robot
2018-06-13  7:29     ` Joel Fernandes
2018-06-18 16:56       ` Paul E. McKenney
2018-06-18 22:26         ` Joel Fernandes
2018-06-19  1:08           ` Paul E. McKenney
2018-06-19  1:36             ` Joel Fernandes
2018-06-19  2:38               ` Paul E. McKenney
2018-06-11 12:56 ` Paul E. McKenney [this message]

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=20180611125658.GR3593@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=jiangshanlai@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=joelaf@google.com \
    --cc=josh@joshtriplett.org \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@redhat.com \
    --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