From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753869Ab0CZGU5 (ORCPT ); Fri, 26 Mar 2010 02:20:57 -0400 Received: from one.firstfloor.org ([213.235.205.2]:34022 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751883Ab0CZGUz (ORCPT ); Fri, 26 Mar 2010 02:20:55 -0400 Date: Fri, 26 Mar 2010 07:20:54 +0100 From: Andi Kleen To: Thomas Gleixner Cc: Linus Torvalds , LKML , linux-arch@vger.kernel.org, Andrew Morton , Ingo Molnar , Peter Zijlstra , Alan Cox , Andi Kleen , David Miller , Greg Kroah-Hartman , Arnaldo Carvalho de Melo Subject: Re: [patch 2/2] genirq: Remove IRQF_DISABLED from core code Message-ID: <20100326062054.GW20695@one.firstfloor.org> References: <20100326000325.917127328@linutronix.de> <20100326000405.991244690@linutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100326000405.991244690@linutronix.de> User-Agent: Mutt/1.4.2.2i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 26, 2010 at 12:06:55AM -0000, Thomas Gleixner wrote: > Remove all code which is related to IRQF_DISABLED from the core kernel > code. IRQF_DISABLED still exists as a flag, but becomes a NOOP and > will be removed after a grace period. That way we can easily revert to > the previous behaviour by just restoring the core code. Perhaps I'm dense but it's not fully clear to me why is suddenly safe to use the behaviour of this flags on shared interrupts when it wasn't before? -Andi -- ak@linux.intel.com -- Speaking for myself only.