From: Daniel Bristot de Oliveira <bristot@redhat.com>
To: linux-rt-users@vger.kernel.org
Cc: "Luis Claudio R . Goncalves" <lgoncalv@redhat.com>,
Clark Williams <williams@redhat.com>,
Luiz Capitulino <lcapitulino@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [RFC 3/3] rt: Check if the task needs to migrate when re-enabling migration
Date: Fri, 16 Jun 2017 12:39:48 +0200 [thread overview]
Message-ID: <99de119c39e3af618efdb2f79bf30e60ca42a6ec.1497607974.git.bristot@redhat.com> (raw)
In-Reply-To: <cover.1497607974.git.bristot@redhat.com>
In the case of an affinity change during a migrate_disable section,
__set_cpus_allowed_ptr will not try to move the task from a CPU
in which it cannot execute anymore.
So, after enabling migration, if the current task cannot execute in
the current CPU anymore, migrate it away.
Signed-off-by: Daniel Bristot de Oliveira <bristot@redhat.com>
Cc: Luis Claudio R. Goncalves <lgoncalv@redhat.com>
Cc: Clark Williams <williams@redhat.com>
Cc: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
---
kernel/sched/core.c | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 0396bf2..207bc85 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -3462,6 +3462,34 @@ void migrate_enable(void)
task_rq(p)->dl.dl_nr_migratory++;
}
+ /*
+ * Check if the task can still run on this CPU. In the case of an
+ * affinity change during a migrate_disable section,
+ * __set_cpus_allowed_ptr will not try to move the task from a CPU
+ * that the task cannot execute anymore.
+ *
+ * So, if the current task cannot execute in the current CPU anymore,
+ * migrate it away.
+ */
+ if (unlikely(!cpumask_test_cpu(task_cpu(p), &p->cpus_allowed))) {
+ const struct cpumask *cpu_mask = (p->flags & PF_KTHREAD) ?
+ cpu_online_mask : cpu_active_mask;
+
+ int dest_cpu = cpumask_any_and(cpu_mask, &p->cpus_allowed);
+ struct migration_arg arg = {p, dest_cpu};
+
+ /* Need help from migration thread: drop lock and wait. */
+ task_rq_unlock(rq, p, &rf);
+ unpin_current_cpu();
+ preempt_enable();
+ preempt_lazy_enable();
+
+ stop_one_cpu(cpu_of(rq), migration_cpu_stop, &arg);
+ tlb_migrate_finish(p->mm);
+
+ return;
+ }
+
task_rq_unlock(rq, p, &rf);
unpin_current_cpu();
preempt_enable();
--
2.9.4
next prev parent reply other threads:[~2017-06-16 10:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 10:39 [RFC 0/3] rt: Some fixes for migrate_disable/enable Daniel Bristot de Oliveira
2017-06-16 10:39 ` [RFC 1/3] rt: Increase/decrease the nr of migratable tasks when enabling/disabling migration Daniel Bristot de Oliveira
2017-06-16 10:39 ` [RFC 2/3] rt: Update nr_cpus_allowed if the affinity of a task changes while its migration is disabled Daniel Bristot de Oliveira
2017-06-16 10:39 ` Daniel Bristot de Oliveira [this message]
2017-06-16 16:58 ` [RFC 3/3] rt: Check if the task needs to migrate when re-enabling migration Sebastian Andrzej Siewior
2017-06-23 13:14 ` Sebastian Andrzej Siewior
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=99de119c39e3af618efdb2f79bf30e60ca42a6ec.1497607974.git.bristot@redhat.com \
--to=bristot@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=lcapitulino@redhat.com \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=williams@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;
as well as URLs for NNTP newsgroup(s).