Home
last modified time | relevance | path

Searched refs:waker (Results 1 – 6 of 6) sorted by relevance

/linux-2.6.39/tools/perf/
Dbuiltin-timechart.c142 int waker; member
437 we->waker = pid; in sched_wakeup()
440 we->waker = -1; in sched_wakeup()
702 if (p->pid == we->waker || p->pid == we->wakee) { in draw_wakeups()
706 if (p->pid == we->waker && !from) { in draw_wakeups()
719 if (p->pid == we->waker && !from) { in draw_wakeups()
735 sprintf(task_from, "[%i]", we->waker); in draw_wakeups()
742 if (we->waker == -1) in draw_wakeups()
Dbuiltin-sched.c769 struct task_desc *waker, *wakee; in replay_wakeup_event() local
780 waker = register_pid(wakeup_event->common_pid, "<unknown>"); in replay_wakeup_event()
783 add_sched_event_wakeup(waker, timestamp, wakee); in replay_wakeup_event()
/linux-2.6.39/drivers/bluetooth/
Dbtusb.c189 struct work_struct waker; member
625 cancel_work_sync(&data->waker); in btusb_close()
743 schedule_work(&data->waker); in btusb_send_frame()
873 struct btusb_data *data = container_of(work, struct btusb_data, waker); in btusb_waker()
952 INIT_WORK(&data->waker, btusb_waker); in btusb_probe()
/linux-2.6.39/Documentation/
Dfutex-requeue-pi.txt110 FUTEX_REQUEUE_CMP_PI is called by the waker
Drobust-futexes.txt17 waiter with the waker - without them having to know about each other.
Dmemory-barriers.txt1355 The available waker functions include:
1374 [!] Note that the memory barriers implied by the sleeper and the waker do _not_
1385 and the waker does:
1402 and the waker should do: