From: Peter Zijlstra <peterz@infradead.org>
To: Wanpeng Li <wanpeng.li@linux.intel.com>
Cc: Wanpeng Li <kernellwp@gmail.com>, Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@arm.com>,
Kirill Tkhai <ktkhai@parallels.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2] sched/deadline: support dl task migration during cpu hotplug
Date: Thu, 6 Nov 2014 11:08:23 +0100 [thread overview]
Message-ID: <20141106100823.GR10501@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20141106014634.GA25640@kernel>
On Thu, Nov 06, 2014 at 09:46:34AM +0800, Wanpeng Li wrote:
> >Ah, it could be that for offline cpus we have a singleton rd. Lemme try
>
> I still cannot find where build the singleton rd in the codes, could you
> point out?
So this is all quite horrible code, but what I think happens is that:
sched_cpu_inactive() -> set_cpu_active(cpu, false);
cpuset_cpu_inactive() -> cpuset_update_active_cpus(false)
-> partition_sched_domains(1, NULL, NULL)
-> build_sched_domains(cpu_active_mask)
-> for_each_cpu()
cpu_attach_domain() -> rq_attach_root()
Now, that will detach all active cpus from the current root domain and
attach them to the new root domain. Which leaves behind the old root
domain attached to only the one 'dead' cpu.
next prev parent reply other threads:[~2014-11-06 10:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 8:51 [RFC PATCH v2] sched/deadline: support dl task migration during cpu hotplug Wanpeng Li
2014-11-05 10:08 ` Juri Lelli
2014-11-05 10:35 ` Wanpeng Li
2014-11-05 10:50 ` Peter Zijlstra
2014-11-05 10:59 ` Wanpeng Li
2014-11-05 12:52 ` Peter Zijlstra
2014-11-06 1:46 ` Wanpeng Li
2014-11-06 10:08 ` Peter Zijlstra [this message]
2014-11-06 11:31 ` Wanpeng Li
2014-11-05 13:14 ` Kirill Tkhai
2014-11-05 16:25 ` 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=20141106100823.GR10501@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=juri.lelli@arm.com \
--cc=kernellwp@gmail.com \
--cc=ktkhai@parallels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=wanpeng.li@linux.intel.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 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.