On Friday, June 25, 2010, Florian Mickler wrote: > On Thu, 24 Jun 2010 13:09:27 -0400 (EDT) > Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > > > > > This requires you to define an explicit PCI_WAKEUP_COOLDOWN delay. I > > > > think that's okay; I had to do something similar with USB and SCSI. > > > > (And I still think it would be a good idea to prevent workqueue threads > > > > from freezing until their queues are empty.) > > I'm not that familiar with the freezer, but couldn't it be > deadlocky if the work depends on some already frozen part? No, in the case of freezable workqueues (which is the one we're discussing) they generally can't depend on anything freezable, because it's never known which freezable tasks will be frozen first. > What about a new work-type that calls > pm_relax() after executing it's workfunction and executing > pm_stay_awake() on enqueue? That might be useful., although it doesn't really help here, because there still is a window between queuing up a work item and executing it. Rafael _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
