From: Peter Zijlstra <peterz@infradead.org>
To: Joonwoo Park <joonwoop@codeaurora.org>
Cc: Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] sched: fix incorrect wait time and wait count statistics
Date: Sun, 25 Oct 2015 11:26:10 +0100 [thread overview]
Message-ID: <20151025102610.GQ2508@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <1445750594-14078-1-git-send-email-joonwoop@codeaurora.org>
On Sat, Oct 24, 2015 at 10:23:14PM -0700, Joonwoo Park wrote:
> @@ -1069,7 +1069,7 @@ static struct rq *move_queued_task(struct rq *rq, struct task_struct *p, int new
> {
> lockdep_assert_held(&rq->lock);
>
> - dequeue_task(rq, p, 0);
> + dequeue_task(rq, p, DEQUEUE_MIGRATING);
> p->on_rq = TASK_ON_RQ_MIGRATING;
> set_task_cpu(p, new_cpu);
> raw_spin_unlock(&rq->lock);
> @@ -5656,7 +5671,7 @@ static void detach_task(struct task_struct *p, struct lb_env *env)
> {
> lockdep_assert_held(&env->src_rq->lock);
>
> - deactivate_task(env->src_rq, p, 0);
> + deactivate_task(env->src_rq, p, DEQUEUE_MIGRATING);
> p->on_rq = TASK_ON_RQ_MIGRATING;
> set_task_cpu(p, env->dst_cpu);
> }
Also note that on both sites we also set TASK_ON_RQ_MIGRATING -- albeit
late. Can't you simply set that earlier (and back to QUEUED later) and
test for task_on_rq_migrating() instead of blowing up the fastpath like
you did?
next prev parent reply other threads:[~2015-10-25 10:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-25 5:23 [PATCH] sched: fix incorrect wait time and wait count statistics Joonwoo Park
2015-10-25 10:08 ` Peter Zijlstra
2015-10-25 10:26 ` Peter Zijlstra [this message]
2015-10-27 1:44 ` Joonwoo Park
2015-10-27 12:57 ` Peter Zijlstra
2015-10-28 2:40 ` Joonwoo Park
2015-10-28 4:46 ` [PATCH v4] " Joonwoo Park
2015-11-06 13:57 ` Peter Zijlstra
2015-11-07 2:41 ` Joonwoo Park
2015-11-09 10:32 ` Peter Zijlstra
2015-11-13 3:38 ` [PATCH v5] " Joonwoo Park
2015-11-23 16:20 ` [tip:sched/core] sched/core: Fix " tip-bot for Joonwoo Park
2015-10-27 19:17 ` [PATCH v3] sched: fix " Joonwoo Park
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=20151025102610.GQ2508@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=joonwoop@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.