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 _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
