From: Peter Zijlstra <peterz@infradead.org>
To: Olav Haugan <ohaugan@codeaurora.org>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] sched: Update task->on_rq when tasks are moving between runqueues
Date: Sun, 25 Oct 2015 11:09:24 +0100 [thread overview]
Message-ID: <20151025100924.GP2508@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <1445709662-17232-1-git-send-email-ohaugan@codeaurora.org>
On Sat, Oct 24, 2015 at 11:01:02AM -0700, Olav Haugan wrote:
> Task->on_rq has three states:
> 0 - Task is not on runqueue (rq)
> 1 (TASK_ON_RQ_QUEUED) - Task is on rq
> 2 (TASK_ON_RQ_MIGRATING) - Task is on rq but in the process of being
> migrated to another rq
>
> When a task is moving between rqs task->on_rq state should be
> TASK_ON_RQ_MIGRATING
Only when not holding both rq locks..
next prev parent reply other threads:[~2015-10-25 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-24 18:01 [PATCH] sched: Update task->on_rq when tasks are moving between runqueues Olav Haugan
2015-10-25 10:09 ` Peter Zijlstra [this message]
2015-10-29 0:57 ` Olav Haugan
2015-10-29 1:58 ` Peter Zijlstra
2015-11-02 20:40 ` Paul Turner
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=20151025100924.GP2508@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ohaugan@codeaurora.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.