From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Gleixner Subject: Re: [patch 1/2] genirq: Run irq handlers with interrupts disabled Date: Wed, 31 Mar 2010 13:16:37 +0200 (CEST) Message-ID: References: <20100326000325.917127328@linutronix.de> <20100326000405.758579387@linutronix.de> <20100326061310.GV20695@one.firstfloor.org> <20100330053325.GL20695@one.firstfloor.org> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: Received: from www.tglx.de ([62.245.132.106]:38059 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753187Ab0CaLTU (ORCPT ); Wed, 31 Mar 2010 07:19:20 -0400 In-Reply-To: <20100330053325.GL20695@one.firstfloor.org> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Andi Kleen Cc: Linus Torvalds , LKML , linux-arch@vger.kernel.org, Andrew Morton , Ingo Molnar , Peter Zijlstra , Alan Cox , David Miller , Greg Kroah-Hartman , Arnaldo Carvalho de Melo On Tue, 30 Mar 2010, Andi Kleen wrote: > > Why not simply force IRQF_DISABLED for all MSI interrupts. That still > > allows nesting for non MSI ones, but it limits the chance of throwing > > up reasonably well. That's a two liner. > > > > Can you please test whether it resolves the issue at hand ? > > Sorry for the late answer. Got confirmation that this patch > fixes the test case. Thanks. Ok, I'll push it linus wards and cc stable. I think thats the least intrusive safe bet we can have right now. Thanks, tglx