Searched refs:sleeper (Results 1 – 5 of 5) sorted by relevance
10 setup.o sleeper.o dma.o dbdma.o vss.o irq.o usb.o
11 obj-$(CONFIG_SUSPEND) += pm.o sleeper.o
49 def __init__(self, sleeper): argument50 self.sleeper = sleeper53 return "%s gone to sleep" % thread_name(self.sleeper)
654 struct thread_deferred_req sleeper; in cache_wait_req() local655 struct cache_deferred_req *dreq = &sleeper.handle; in cache_wait_req()657 sleeper.completion = COMPLETION_INITIALIZER_ONSTACK(sleeper.completion); in cache_wait_req()664 &sleeper.completion, req->thread_wait) <= 0) { in cache_wait_req()669 if (!hlist_unhashed(&sleeper.handle.hash)) { in cache_wait_req()670 __unhash_deferred_req(&sleeper.handle); in cache_wait_req()679 wait_for_completion(&sleeper.completion); in cache_wait_req()
2158 Firstly, the sleeper normally follows something like this sequence of events:2266 [!] Note that the memory barriers implied by the sleeper and the waker do _not_2268 values after the sleeper has called set_current_state(). For instance, if the2269 sleeper does:2284 the sleeper as coming after the change to my_data. In such a circumstance, the2286 separate data accesses. Thus the above sleeper ought to do: