From: Kirill Tkhai <tkhai@yandex.ru>
To: Peter Zijlstra <peterz@infradead.org>,
"riel@redhat.com" <riel@redhat.com>,
"laijs@cn.fujitsu.com" <laijs@cn.fujitsu.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@kernel.org" <mingo@kernel.org>
Subject: Re: [PATCH] sched: Fix migration_cpu_stop() return value
Date: Wed, 04 Jun 2014 15:18:45 +0400 [thread overview]
Message-ID: <5962011401880725@web26h.yandex.ru> (raw)
In-Reply-To: <20140604104122.GL30445@twins.programming.kicks-ass.net>
Hi, Peter,
04.06.2014, 14:41, "Peter Zijlstra" <peterz@infradead.org>:
> A while ago I did a similar patch for some debugging, but looking at it
> again today I realized we should probably fix this anyway.
>
> ---
> Subject: sched: Fix migration_cpu_stop() return value
>
> There are a number of migration_cpu_stop() users; and some actually care
> about the success of the migration. So report this.
>
> In particular migrate_task_to() as used from task_numa_migrate()
> actually tests this return value.
>
> Also change set_cpus_allowed_ptr() to propagate this return value, since
> it already returns other errors.
>
> Cc: Lai Jiangshan <laijs@cn.fujitsu.com>
> Cc: Ingo Molnar <mingo@redhat.com>
> Signed-off-by: Peter Zijlstra <peterz@infradead.org>
> ---
> kernel/sched/core.c | 15 +++++++++++----
> 1 file changed, 11 insertions(+), 4 deletions(-)
(snipped everything because of bad email editor)
In set_cpus_allowed_ptr() p->on_rq branch can not fail.
We've changed affinity and released rq's lock, so task can migrate
on allowed cpu only (even if migration_cpu_stop fails).
And it's a little ambiguously how user should react on this EAGAIN.
Regards,
Kirill.
next prev parent reply other threads:[~2014-06-04 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 10:41 [PATCH] sched: Fix migration_cpu_stop() return value Peter Zijlstra
2014-06-04 11:10 ` Lai Jiangshan
2014-06-04 11:18 ` Kirill Tkhai [this message]
2014-06-04 12:03 ` Peter Zijlstra
2014-06-04 12:29 ` 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=5962011401880725@web26h.yandex.ru \
--to=tkhai@yandex.ru \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@redhat.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