> On powerbooks you disable the nonboot CPUs before suspending devices, which > simplifies things _a_ _lot_ in comparison with the general case. Not that much actually. It avoids having to gather them all in the last stage at the low level but that isn't really related to what we are talking about right now. > If you additionally disable kernel preemption, then you don't need anything > like the freezer anyway in that case (except for detecting situations in which > the suspend process can deadlock with a task stuck in the D state holding a > lock, but that's overkill). kernel preemption and SMP have nothing to do with it. You can still schedule because one of the driver suspend() callback is schedul'ing, maybe waiting for some requests to complete, etc... Happens typically with the disk suspend callbacks. I agree that it does lower the likelyness of having a userspace process pound on the wrong driver at the wrong time though. Ben. _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
