Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753676Ab0DAGfx (ORCPT ); Thu, 1 Apr 2010 02:35:53 -0400 Received: from smtp1.linux-foundation.org ([140.211.169.13]:54552 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752586Ab0DAGfq (ORCPT ); Thu, 1 Apr 2010 02:35:46 -0400 Date: Wed, 31 Mar 2010 23:33:30 -0400 From: Andrew Morton To: "H. Peter Anvin" Cc: Benjamin Herrenschmidt , Christoph Lameter , Matthew Wilcox , Yinghai Lu , Rabin Vincent , lkml , penberg@cs.helsinki.fi, linux-arch@vger.kernel.org Subject: Re: start_kernel(): bug: interrupts were enabled early Message-Id: <20100331233330.1a7357e4.akpm@linux-foundation.org> In-Reply-To: <4BB43CAC.3080102@zytor.com> References: <20100325194100.GA2364@debian> <20100331134048.da4e35a7.akpm@linux-foundation.org> <4BB3B4DB.7040904@kernel.org> <20100331210145.GB32165@parisc-linux.org> <4BB3B8FC.1020608@zytor.com> <20100331211754.GC32165@parisc-linux.org> <20100331215411.GB17715@flint.arm.linux.org.uk> <4BB3C540.9000405@zytor.com> <1270075071.7101.79.camel@pasglop> <20100331154955.54176e5e.akpm@linux-foundation.org> <1270084631.7101.81.camel@pasglop> <20100331182654.d36c87ff.akpm@linux-foundation.org> <4BB43CAC.3080102@zytor.com> X-Mailer: Sylpheed 2.7.1 (GTK+ 2.18.7; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 885 Lines: 23 On Wed, 31 Mar 2010 23:26:52 -0700 "H. Peter Anvin" wrote: > On 03/31/2010 03:26 PM, Andrew Morton wrote: > > > > Not by adding overhead to every single down_read()/down_write() just to > > fix a once-off startup problem - that's taking laziness way too far. > > > > How much overhead is this on non-x86 architectures (keep in mind x86 > doesn't use this?) > Just a few instructions, I guess. But we can do it with zero. And from a design POV, pretending that down_read()/down_write() can be called with interrupts disabled is daft - they cannot! Why muck up the usual code paths with this startup-specific hack? -- 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/