Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261198AbUKCAXb (ORCPT ); Tue, 2 Nov 2004 19:23:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261211AbUKCAXb (ORCPT ); Tue, 2 Nov 2004 19:23:31 -0500 Received: from gate.crashing.org ([63.228.1.57]:26297 "EHLO gate.crashing.org") by vger.kernel.org with ESMTP id S261295AbUKBXnE (ORCPT ); Tue, 2 Nov 2004 18:43:04 -0500 Subject: Re: [PATCH] PPC64 mmu_context_init needs to run earlier From: Benjamin Herrenschmidt To: Linus Torvalds Cc: Nathan Lynch , Andrew Morton , Paul Mackerras , Anton Blanchard , Linux Kernel list In-Reply-To: References: <16775.5912.788675.644838@cargo.ozlabs.ibm.com> <20041101221336.5f6d8534.akpm@osdl.org> <1099432625.23845.93.camel@pants.austin.ibm.com> Content-Type: text/plain Date: Wed, 03 Nov 2004 10:35:00 +1100 Message-Id: <1099438500.20295.47.camel@gaston> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1021 Lines: 26 > 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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/