Searched refs:woke (Results 1 – 6 of 6) sorted by relevance
| /Linux-v4.19/samples/bpf/ |
| D | offwaketime_kern.c | 64 struct wokeby_t woke; in waker() local
69 bpf_get_current_comm(&woke.name, sizeof(woke.name)); in waker()
70 woke.ret = bpf_get_stackid(ctx, &stackmap, STACKID_FLAGS); in waker()
72 bpf_map_update_elem(&wokeby, &pid, &woke, BPF_ANY); in waker()
78 struct wokeby_t *woke; in update_counts() local
87 woke = bpf_map_lookup_elem(&wokeby, &pid); in update_counts()
88 if (woke) { in update_counts()
89 key.wret = woke->ret; in update_counts()
90 __builtin_memcpy(&key.waker, woke->name, sizeof(key.waker)); in update_counts()
|
| /Linux-v4.19/Documentation/driver-api/usb/ |
| D | persist.rst | 35 system woke up, who cares? It'll still work the same when you type on
|
| /Linux-v4.19/Documentation/media/v4l-drivers/ |
| D | zoran.rst | 472 I woke up, and can't go to sleep again. I'll kill some time explaining why
|
| /Linux-v4.19/Documentation/locking/ |
| D | rt-mutex-design.txt | 522 in the slow path too. If a waiter of a mutex woke up because of a signal
|
| /Linux-v4.19/Documentation/trace/ |
| D | ftrace.rst | 1768 just 15 microseconds from the time it woke up, to the time it
|
| /Linux-v4.19/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 3041 reason and never woke up.
|
