Searched refs:sleeper (Results 1 – 7 of 7) sorted by relevance
9 setup.o sleeper.o dma.o dbdma.o vss.o irq.o usb.o
47 def __init__(self, sleeper): argument48 self.sleeper = sleeper51 return "%s gone to sleep" % thread_name(self.sleeper)
586 struct thread_deferred_req sleeper; in cache_wait_req() local587 struct cache_deferred_req *dreq = &sleeper.handle; in cache_wait_req()589 sleeper.completion = COMPLETION_INITIALIZER_ONSTACK(sleeper.completion); in cache_wait_req()596 &sleeper.completion, req->thread_wait) <= 0) { in cache_wait_req()601 if (!hlist_unhashed(&sleeper.handle.hash)) { in cache_wait_req()602 __unhash_deferred_req(&sleeper.handle); in cache_wait_req()611 wait_for_completion(&sleeper.completion); in cache_wait_req()
107 struct task_struct *sleeper; /* this process */ member722 wake_up_process(q->sleeper); in wake_up_sem_queue_do()1951 queue.sleeper = current; in SYSCALL_DEFINE4()
84 API-wq-has-sleeper
110 API-struct-hrtimer-sleeper
1952 Firstly, the sleeper normally follows something like this sequence of events:2047 [!] Note that the memory barriers implied by the sleeper and the waker do _not_2049 values after the sleeper has called set_current_state(). For instance, if the2050 sleeper does:2065 the sleeper as coming after the change to my_data. In such a circumstance, the2067 separate data accesses. Thus the above sleeper ought to do: