From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Nathan Lynch <nathanl@austin.ibm.com>,
Andrew Morton <akpm@osdl.org>, Paul Mackerras <paulus@samba.org>,
Anton Blanchard <anton@samba.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PPC64 mmu_context_init needs to run earlier
Date: Wed, 03 Nov 2004 10:35:00 +1100 [thread overview]
Message-ID: <1099438500.20295.47.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.58.0411021406010.2187@ppc970.osdl.org>
> That said, maybe the problem is that we shouldn't even get far enough into
> the fork() logic to ever get into a new MMU context if driver_init ends up
> being called before we're ready.
Agreed. I chatted with Andrew about this, and I think we need
call_usermodehelper to be in a "plugged" state during boot, where it
queues up events but doesn't exec's userland. It remains to be decided
at what point during boot (during initcalls ? after initcalls) we can
"unplug" it tho...
I think it's definitely bogus to try to run userland in the middle of
arch_initcall's....
We need this plug/unplug logic (as I wrote separately to linux-pm) for
suspend as well, since we can't affort calling userlands once we have
started suspending devices (and frozen userland).
Ben.
next prev parent reply other threads:[~2004-11-03 0:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 5:11 Paul Mackerras
2004-11-02 6:13 ` Andrew Morton
2004-11-02 21:57 ` Nathan Lynch
2004-11-02 22:10 ` Linus Torvalds
2004-11-02 23:35 ` Benjamin Herrenschmidt [this message]
2004-11-03 0:08 ` Nathan Lynch
2004-11-03 23:04 ` Andrew Morton
2004-11-04 2:53 ` Paul Mackerras
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=1099438500.20295.47.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathanl@austin.ibm.com \
--cc=paulus@samba.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®