Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754203AbZCKW2Z (ORCPT ); Wed, 11 Mar 2009 18:28:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752479AbZCKW2Q (ORCPT ); Wed, 11 Mar 2009 18:28:16 -0400 Received: from www.tglx.de ([62.245.132.106]:34806 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752456AbZCKW2P (ORCPT ); Wed, 11 Mar 2009 18:28:15 -0400 Date: Wed, 11 Mar 2009 23:25:12 +0100 (CET) From: Thomas Gleixner To: Linus Torvalds cc: "Rafael J. Wysocki" , pm list , LKML , Ingo Molnar , "Eric W. Biederman" , Benjamin Herrenschmidt , Jeremy Fitzhardinge , Len Brown , Jesse Barnes , Frans Pop , =?ISO-8859-15?Q?Arve_Hj=F8nnev=E5g?= Subject: Re: [PATCH 1/10] PM: Rework handling of interrupts during suspend-resume (rev. 5) In-Reply-To: Message-ID: References: <200902221837.49396.rjw@sisk.pl> <200903112215.02445.rjw@sisk.pl> <200903112250.10572.rjw@sisk.pl> 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: 892 Lines: 26 On Wed, 11 Mar 2009, Linus Torvalds wrote: > On Wed, 11 Mar 2009, Thomas Gleixner wrote: > > > > I'm not worried about nested ones. > > Then you shouldn't be worried about IRQ_SUSPENDED at all, since that one > increments the disabled depth count. > > So _all_ disable/enable_irq calls will by definition be nested inside > IRQ_SUSPENDED. Right, if they are in disable -> enable order. But the stupid stray enable will be visible either by wrecking the suspend with hard to debug failures or trigger the depth check in the resume code. I'm burned enough by the timer failures which pop up long after the real bug happened. Thanks, 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/