From: Peter Zijlstra <peterz@infradead.org>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Tejun Heo <tj@kernel.org>, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH/RFC] timer: fix deadlock on cpu hotplug
Date: Sat, 25 Sep 2010 02:19:47 +0200 [thread overview]
Message-ID: <1285373987.2275.1048.camel@laptop> (raw)
In-Reply-To: <20100923133103.GA3832@osiris.boeblingen.de.ibm.com>
On Thu, 2010-09-23 at 15:31 +0200, Heiko Carstens wrote:
> On Wed, Sep 22, 2010 at 04:29:36PM +0200, Peter Zijlstra wrote:
> > On Wed, 2010-09-22 at 11:22 +0200, Peter Zijlstra wrote:
> >
> > > The idea was to move it to a class of its own above SCHED_FIFO.
> > >
> > > I'll try and get something done, but I'm heading out to LinuxCon.JP
> > > soon.
> >
> > Something like the below, it seems to boot, build a kernel and hotplug.
>
> Thanks for the fast patch. Yes, it works. Sort of:
>
> ------------[ cut here ]------------
<SPLAT>
>
> ..and crashes afterwards ;)
Yeah, I can imagine,. weird though, kthread_create() should leave the
new thread in uninterruptible context. The above warning implies this is
not so..
> Btw. I also tried to boot 2.6.35.5 with your patch and it hangs just at
> the beginning. I also had to apply 5e3d20a68f63fc5a310687d81956c3b96e488b84
> "init: Remove the BKL from startup code" to make the machine boot again,
> which was a bit surprising.
Most curious and unexpected,.. I'll try and have a look, but it might
have to wait until after LinuxCon.JP..
next prev parent reply other threads:[~2010-09-25 0:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 14:20 [PATCH/RFC] timer: fix deadlock on cpu hotplug Heiko Carstens
2010-09-21 15:36 ` Tejun Heo
2010-09-21 15:40 ` Peter Zijlstra
2010-09-22 8:37 ` Heiko Carstens
2010-09-22 9:22 ` Peter Zijlstra
2010-09-22 14:29 ` Peter Zijlstra
2010-09-23 13:31 ` Heiko Carstens
2010-09-25 0:19 ` Peter Zijlstra [this message]
2010-10-11 12:31 ` Peter Zijlstra
2010-10-11 13:51 ` Heiko Carstens
2010-10-18 19:16 ` [tip:sched/core] sched: Create special class for stop/migrate work tip-bot for Peter Zijlstra
2010-09-21 15:39 ` [PATCH/RFC] timer: fix deadlock on cpu hotplug Thomas Gleixner
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=1285373987.2275.1048.camel@laptop \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=tj@kernel.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.