On Tue, 29 Mar 2005 23:12:39 +0200, Pavel Machek <[EMAIL PROTECTED]> wrote: > > > > I am leaning towards calling disable_usermodehelper (not writtent yet) > > after swsusp completes snapshotting memory. We really don't care about > > hotplug events in this case and this will allow keeping "normal" > > resume in drivers as is. What do you think? > > That would certianly do the trick. > > [Or perhaps in_suspend() is slightly nicer solution? People wanted it > for other stuff (sanity checking, like BUG_ON(in_suspend())), too....] >
We might want having both... Hmm... in_suspend - is it only for swsusp (in_swsusp) or for suspend-to-ram as well? For suspend to ram we might need slightly different rules, I don't know. A separate call will allow more fine-grained control and will explicitely tell reader what is happening. I do not have a strong preference though. -- Dmitry - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
