From: Kirill Tkhai <ktkhai@parallels.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@kernel.org>,
<tkhai@yandex.ru>, Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
"Mike Galbraith" <umgwanakikbuti@gmail.com>,
Konstantin Khorenko <khorenko@parallels.com>
Subject: Re: [PATCH 3/3] sched: Rework check_for_tasks()
Date: Mon, 23 Jun 2014 14:52:18 +0400 [thread overview]
Message-ID: <1403520738.3462.11.camel@tkhai> (raw)
In-Reply-To: <20140623102457.GW19860@laptop.programming.kicks-ass.net>
В Пн, 23/06/2014 в 12:24 +0200, Peter Zijlstra пишет:
> On Tue, Jun 17, 2014 at 05:24:22PM +0400, Kirill Tkhai wrote:
> >
> > 1)Iterate throw all of threads in the system.
>
> thru
Thanks :)
>
> > Check for all threads, not only for group leaders.
> >
> > 2)Check for p->on_rq instead of p->state and cputime.
> > Preempted task in !TASK_RUNNING state OR just
> > created task may be queued, that we want to be
> > reported too.
> >
> > 3)Use read_lock() instead of write_lock().
> > This function does not change any structures, and
> > read_lock() is enough.
> >
> > Signed-off-by: Kirill Tkhai <ktkhai@parallels.com>
> > CC: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
> > CC: Mike Galbraith <umgwanakikbuti@gmail.com>
> > CC: Peter Zijlstra <peterz@infradead.org>
> > CC: Ingo Molnar <mingo@kernel.org>
> > ---
> > kernel/cpu.c | 33 ++++++++++++++++++++-------------
> > 1 file changed, 20 insertions(+), 13 deletions(-)
> >
> > diff --git a/kernel/cpu.c b/kernel/cpu.c
> > index a343bde..81e2a38 100644
> > --- a/kernel/cpu.c
> > +++ b/kernel/cpu.c
> > @@ -274,21 +274,28 @@ void clear_tasks_mm_cpumask(int cpu)
> > rcu_read_unlock();
> > }
> >
> > -static inline void check_for_tasks(int cpu)
> > +static inline void check_for_tasks(int dead_cpu)
> > {
> > - struct task_struct *p;
> > - cputime_t utime, stime;
> > + struct task_struct *g, *p;
> >
> > - write_lock_irq(&tasklist_lock);
> > - for_each_process(p) {
> > - task_cputime(p, &utime, &stime);
> > - if (task_cpu(p) == cpu && p->state == TASK_RUNNING &&
> > - (utime || stime))
> > - pr_warn("Task %s (pid = %d) is on cpu %d (state = %ld, flags = %x)\n",
> > - p->comm, task_pid_nr(p), cpu,
> > - p->state, p->flags);
> > - }
> > - write_unlock_irq(&tasklist_lock);
> > + read_lock_irq(&tasklist_lock);
> > + do_each_thread(g, p) {
> > + if (!p->on_rq)
> > + continue;
> > + /*
> > + * We do the check with unlocked task_rq(p)->lock.
> > + * Order the reading to do not warn about a task,
> > + * which was running on this cpu in the past, and
> > + * it's just been woken on another cpu.
> > + */
> > + rmb();
>
> smp_rmb();
>
> > + if (task_cpu(p) != dead_cpu)
> > + continue;
>
> But because we don't have rq->lock held, we can be in the middle of a
> wakeup and miss a task.
>
> Then again, I suppose anything without rq->lock can and will miss tasks.
If we use rq->lock it's possible to move check_for_tasks() to kernel/sched/core.c.
And we can leave TASK_RUNNING check for waking tasks. Maybe something like this?
static inline void check_for_tasks(int dead_cpu)
{
struct task_struct *g, *p;
struct rq *rq = cpu_rq(dead_cpu);
read_lock_irq(&tasklist_lock);
raw_spin_lock(&rq->lock)
do_each_thread(g, p) {
if (!p->on_rq && p->state != TASK_RUNNING)
continue;
if (task_cpu(p) != dead_cpu)
continue;
pr_warn("Task %s (pid=%d) is on cpu %d (state=%ld, flags=%x)\n",
p->comm, task_pid_nr(p), dead_cpu, p->state, p->flags);
} while_each_thread(g, p);
raw_spin_unlock(&rq->lock)
read_unlock_irq(&tasklist_lock);
}
It still does not give a 100% guarantee... Should we take p->pi_lock for every task?
> > + pr_warn("Task %s (pid=%d) is on cpu %d (state=%ld, flags=%x)\n",
> > + p->comm, task_pid_nr(p), dead_cpu, p->state, p->flags);
> > + } while_each_thread(g, p);
> > + read_unlock_irq(&tasklist_lock);
> > }
> >
> > struct take_cpu_down_param {
> >
> >
> >
Regards,
Kirill
next prev parent reply other threads:[~2014-06-23 10:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140617130442.29933.54945.stgit@tkhai>
2014-06-17 13:24 ` [PATCH 1/3] sched/fair: Disable runtime_enabled on dying rq Kirill Tkhai
2014-06-23 10:07 ` Peter Zijlstra
2014-06-23 10:58 ` Kirill Tkhai
2014-06-23 17:29 ` bsegall
2014-06-23 20:49 ` Kirill Tkhai
2014-06-23 21:05 ` bsegall
2014-06-23 21:15 ` Kirill Tkhai
2014-06-17 13:24 ` [PATCH 2/3] sched/rt: __disable_runtime: Enqueue just unthrottled rt_rq back on the stack Kirill Tkhai
2014-06-23 10:12 ` Peter Zijlstra
2014-06-17 13:24 ` [PATCH 3/3] sched: Rework check_for_tasks() Kirill Tkhai
2014-06-23 10:24 ` Peter Zijlstra
2014-06-23 10:52 ` Kirill Tkhai [this message]
2014-06-23 14:21 ` 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=1403520738.3462.11.camel@tkhai \
--to=ktkhai@parallels.com \
--cc=khorenko@parallels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=tkhai@yandex.ru \
--cc=umgwanakikbuti@gmail.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