From: Max Krasnyansky <maxk@qualcomm.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Oleg Nesterov <oleg@tv-sign.ru>,
Andrew Morton <akpm@linux-foundation.org>,
Gautham R Shenoy <ego@in.ibm.com>, Paul Jackson <pj@sgi.com>,
Paul Menage <menage@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Vegard Nossum <vegard.nossum@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] S390 topology: don't use kthread() for arch_reinit_sched_domains()
Date: Mon, 30 Jun 2008 12:01:16 -0700 [thread overview]
Message-ID: <48692D7C.10403@qualcomm.com> (raw)
In-Reply-To: <20080630134537.GC7686@osiris.boeblingen.de.ibm.com>
Heiko Carstens wrote:
> On Sun, Jun 29, 2008 at 08:51:32PM +0400, Oleg Nesterov wrote:
>> static void topology_work_fn(struct work_struct *work)
>> {
>> - /* We can't call arch_reinit_sched_domains() from a multi-threaded
>> - * workqueue context since it may deadlock in case of cpu hotplug.
>> - * So we have to create a kernel thread in order to call
>> - * arch_reinit_sched_domains().
>> - */
>> - kthread_run(topology_kthread, NULL, "topology_update");
>> + arch_reinit_sched_domains();
>
> Thank you! Tested and still works ;)
btw Ideally we should not be calling arch_reinit_sched_domains() here
because it'll nuke all sched domains created by the cpuset. We should
instead notify cpusets subsystem and let it rebuild sched domains. In
order to do that we either have to make rebuild_sched_domains() callable
from any context or change arch_init_sched_domains() to no destroy
current domains. Paul M. sent some patches to address first option and
I'm working on the second option.
Max
next prev parent reply other threads:[~2008-06-30 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-29 16:51 [PATCH 2/2] S390 topology: don't use kthread() for arch_reinit_sched_domains() Oleg Nesterov
2008-06-30 13:45 ` Heiko Carstens
2008-06-30 19:01 ` Max Krasnyansky [this message]
2008-06-30 19:33 ` Paul Jackson
2008-06-30 19:49 ` Max Krasnyansky
2008-06-30 20:28 ` Paul Jackson
2008-06-30 20:47 ` Max Krasnyansky
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=48692D7C.10403@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=akpm@linux-foundation.org \
--cc=ego@in.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=oleg@tv-sign.ru \
--cc=peterz@infradead.org \
--cc=pj@sgi.com \
--cc=vegard.nossum@gmail.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