From: Peter Zijlstra <peterz@infradead.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Dominik Dingel <dingel@linux.vnet.ibm.com>,
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:35:39 +0200 [thread overview]
Message-ID: <20150918113539.GL3604@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <55FBF4FD.6060609@redhat.com>
On Fri, Sep 18, 2015 at 01:26:53PM +0200, Paolo Bonzini wrote:
> > +++ 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.
In which case:
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
prev parent reply other threads:[~2015-09-18 11:41 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
2015-09-18 11:30 ` Dominik Dingel
2015-09-18 11:35 ` Peter Zijlstra [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=20150918113539.GL3604@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dingel@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--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