Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752274AbZK3O0S (ORCPT ); Mon, 30 Nov 2009 09:26:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751633AbZK3O0S (ORCPT ); Mon, 30 Nov 2009 09:26:18 -0500 Received: from www.tglx.de ([62.245.132.106]:46610 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751228AbZK3O0R (ORCPT ); Mon, 30 Nov 2009 09:26:17 -0500 Date: Mon, 30 Nov 2009 15:24:40 +0100 (CET) From: Thomas Gleixner To: Peter Zijlstra cc: =?ISO-8859-15?Q?Uwe_Kleine-K=F6nig?= , LKML , Linus Torvalds , Alan Cox , David Brownell , Andrew Morton , Ingo Molnar , Nicolas Pitre , Eric Miao , John Stultz , Rusty Russell , Remy Bohmer , Hugh Dickins , Andrea Gallo , Jamie Lokier , linux-arm-kernel@lists.infradead.org, Benjamin Herrenschmidt Subject: Re: Get rid of IRQF_DISABLED - (was [PATCH] genirq: warn about IRQF_SHARED|IRQF_DISABLED) In-Reply-To: <1259589780.26472.18.camel@laptop> Message-ID: References: <1259356206-14843-1-git-send-email-u.kleine-koenig@pengutronix.de> <1259578067-29169-1-git-send-email-u.kleine-koenig@pengutronix.de> <1259589780.26472.18.camel@laptop> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1371 Lines: 42 On Mon, 30 Nov 2009, Peter Zijlstra wrote: > On Mon, 2009-11-30 at 14:54 +0100, Thomas Gleixner wrote: > > The correct solution IMNSHO is to get rid of IRQF_DISABLED and run > > interrupt handlers always with interrupts disabled and require them > > not to reenable interrupts themself. > > > > Thoughts ? > > I'm all for removing that brain damage: > > http://lkml.org/lkml/2009/3/2/33 Darn, I knew that we discussed that before, but my memory tricked me into believing that it was years ago :) > We should convert the broken hardware PIO and 3com interrupt things to > threaded interrupts, and simply mandate all IRQ handlers run short and > with IRQs disabled. The ide stuff seems to be the only one which uses local_irq_enable_in_hardirq() so that at least it tripped over lockdep already. What's the 3com wreckage about ? > Except I guess that will upset some of the IRQ priority folks, like > power, where they (iirc) have a stack per irq prio level. Is that actually used ? Ben ? > But its not like the core kernel knows about these nesting rules and can > actually track any of that muck. True. tglx -- 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/