Searched refs:awakened (Results 1 – 10 of 10) sorted by relevance
| /Linux-v6.1/Documentation/tools/rtla/ |
| D | rtla-timerlat-top.rst | 127 and then when the *timerlat* thread was awakened. This information can
|
| /Linux-v6.1/Documentation/core-api/ |
| D | circular-buffers.rst | 183 is actually awakened. We therefore cannot rely on it for ordering. However,
|
| /Linux-v6.1/tools/perf/ |
| D | builtin-sched.c | 2401 struct thread *awakened) in timehist_print_wakeup_event() argument
2412 timehist_skip_sample(sched, awakened, evsel, sample)) { in timehist_print_wakeup_event()
2426 printf("awakened: %s", timehist_get_commstr(awakened)); in timehist_print_wakeup_event()
|
| /Linux-v6.1/Documentation/RCU/Design/Memory-Ordering/ |
| D | Tree-RCU-Memory-Ordering.rst | 621 callback function and the task being awakened. To see why this is
629 again the callback function and the awakened task must supply proper
|
| /Linux-v6.1/Documentation/admin-guide/ |
| D | kernel-per-CPU-kthreads.rst | 314 having any work to do, so that they are never awakened.
|
| /Linux-v6.1/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| D | Expedited-Grace-Periods.rst | 513 expedited grace period are awakened. A pair of mutexes are used to allow
|
| /Linux-v6.1/Documentation/admin-guide/sysctl/ |
| D | vm.rst | 801 will apply, and the waiter will only be awakened if the lock can be taken.
|
| /Linux-v6.1/Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 2567 awakened, in other words, deadlock has occurred. This same situation of
2667 by battery-powered systems that don't want their idle CPUs to be awakened.
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| D | sysfs-driver-ufs | 1705 read_timeouts is awakened.
|
| /Linux-v6.1/Documentation/ |
| D | memory-barriers.txt | 2218 if something is actually awakened, but otherwise there is no such guarantee.
|
