Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Dominik Dingel <dingel@linux.vnet.ibm.com>,
	Peter Zijlstra <peterz@infradead.org>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ingo Molnar <mingo@redhat.com>,
	Tim Chen <tim.c.chen@linux.intel.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] sched: access local runqueue directly in single_task_running
Date: Fri, 18 Sep 2015 13:26:53 +0200	[thread overview]
Message-ID: <55FBF4FD.6060609@redhat.com> (raw)
In-Reply-To: <1442568465-71559-1-git-send-email-dingel@linux.vnet.ibm.com>



On 18/09/2015 11:27, Dominik Dingel wrote:
> Commit 2ee507c47293 ("sched: Add function single_task_running to let a task
> check if it is the only task running on a cpu") referenced the current
> runqueue with the smp_processor_id.  When CONFIG_DEBUG_PREEMPT is enabled,
> that is only allowed if preemption is disabled or the currrent task is
> bound to the local cpu (e.g. kernel worker).
> 
> With commit f78195129963 ("kvm: add halt_poll_ns module parameter") KVM
> calls single_task_running. If CONFIG_DEBUG_PREEMPT is enabled that
> generates a lot of kernel messages.
> 
> To avoid adding preemption in that cases, as it would limit the usefulness,
> we change single_task_running to access directly the cpu local runqueue.
> 
> Cc: Tim Chen <tim.c.chen@linux.intel.com>
> Suggested-by: Peter Zijlstra <peterz@infradead.org>
> Cc: <stable@vger.kernel.org> # 4.2.x
> Signed-off-by: Dominik Dingel <dingel@linux.vnet.ibm.com>
> ---
>  kernel/sched/core.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index 78b4bad10..5bfad0b 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -2614,13 +2614,13 @@ unsigned long nr_running(void)
>  
>  /*
>   * Check if only the current task is running on the cpu.
> + *
> + * Caution result is subject to time-of-check-to-time-of-use race,
> + * every caller is responsible to set up additional fences if necessary.

Let's expand it a bit more:

 * Caution: this function does not check that the caller has disabled
 * preemption, thus the result might have a time-of-check-to-time-of-use
 * race.  The caller is responsible to use this correctly, for example:
 *
 * - use it from a non-preemptable section
 *
 * - use it from a thread that is bound to a single CPU
 *
 * - use it in a loop where each iteration takes very little time
 *   (e.g. a polling loop)
 */

I'll include it in my pull request.

Paolo

>   */
>  bool single_task_running(void)
>  {
> -	if (cpu_rq(smp_processor_id())->nr_running == 1)
> -		return true;
> -	else
> -		return false;
> +	return raw_rq()->nr_running == 1;
>  }
>  EXPORT_SYMBOL(single_task_running);
>  
> 

  reply	other threads:[~2015-09-18 11:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18  9:27 [PATCH] sched: access local runqueue directly in single_task_running Dominik Dingel
2015-09-18 11:26 ` Paolo Bonzini [this message]
2015-09-18 11:30   ` Dominik Dingel
2015-09-18 11:35   ` Peter Zijlstra

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=55FBF4FD.6060609@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=dingel@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=stable@vger.kernel.org \
    --cc=tim.c.chen@linux.intel.com \
    /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