Home
last modified time | relevance | path

Searched refs:waking (Results 1 – 25 of 25) sorted by relevance

/linux/Documentation/trace/rv/
H A Dmonitor_rtapp.rst124 thread by waking it and waiting for it to exit (`kthread_stop()`). This
128 In the release path of rt_mutex, a boosted task is de-boosted before waking
130 wakeup (e.g. non-real-time task waking real-time task). This is actually
H A Dmonitor_wwnr.rst37 waking the task up. BOOM, the wakeup will happen while the task is
H A Dmonitor_sched.rst268 (``waking`` state) before being switched in again.
286 pending. The task doesn't go through the usual blocking/waking and is set
/linux/Documentation/ABI/testing/
H A Dsysfs-driver-intel-rapid-start20 remain asleep before waking up to enter hibernation.
H A Dsysfs-firmware-acpi42 handoff to the OS waking vector. In nanoseconds.
/linux/Documentation/locking/
H A Dfutex-requeue-pi.rst17 pthread_cond_broadcast() must resort to waking all the tasks waiting
94 requeue call returning to user space and the waiter waking and
H A Drobust-futex-ABI.rst26 waiting on a particular futex, and waking up the next waiter on a
/linux/Documentation/scheduler/
H A Dsched-ext.rst216 The following briefly shows how a waking task is scheduled and executed.
218 1. When a task is waking up, ``ops.select_cpu()`` is the first operation
220 hint. Second, waking up the selected CPU if idle.
227 A side-effect of selecting a CPU is waking it up from idle. While a BPF
/linux/Documentation/networking/
H A Ddriver.rst104 :doc: Lockless queue stopping / waking helpers.
H A Dkcm.rst276 on the socket thus waking up the application thread. When the application
/linux/tools/perf/
H A Dbuiltin-record.c117 unsigned long waking; member
1773 thread->waking++; in record__thread()
2402 thread_data[t].samples, thread_data[t].waking); in record__stop_threads()
2416 unsigned long waking = 0; in record__waking() local
2420 waking += thread_data[t].waking; in record__waking()
2422 return waking; in record__waking()
2782 thread->waking = 0; in __cmd_record()
2806 thread->waking++; in __cmd_record()
/linux/Documentation/driver-api/
H A Dslimbus.rst109 Clock-pause is exited by waking up framer device (if controller driver initiates
/linux/Documentation/trace/coresight/
H A Dcoresight-perf.rst150 be logged, some of it can be lost due to the processor not waking up
/linux/Documentation/core-api/
H A Dcircular-buffers.rst172 * waking anyone up */
/linux/Documentation/admin-guide/pm/
H A Dsuspend-flows.rst196 That usually prevents in-band hardware interrupts from waking up the system,
/linux/drivers/gpu/drm/nouveau/nvkm/engine/sec/fuc/
H A Dg98.fuc0s127 // sleep forver, waking only for interrupts.
/linux/drivers/gpu/drm/nouveau/nvkm/engine/ce/fuc/
H A Dcom.fuc158 // sleep forever, waking for interrupts
/linux/Documentation/hid/
H A Dhid-bpf.rst64 impact the performances by waking up userspace every time there is an
/linux/Documentation/livepatch/
H A Dlivepatch.rst206 user tasks and waking kthreads to patch them. But it could still be
/linux/Documentation/admin-guide/mm/
H A Duserfaultfd.rst158 that waking will be done separately at some later time.
/linux/Documentation/RCU/Design/Expedited-Grace-Periods/
H A DExpedited-Grace-Periods.rst365 Once the grace period completes, Task A starts waking up the tasks
/linux/Documentation/RCU/Design/Memory-Ordering/
H A DTree-RCU-Memory-Ordering.rst170 The approach must be extended to handle one final case, that of waking a
/linux/Documentation/driver-api/usb/
H A Dpower-management.rst325 waking up from hibernation, as many systems do not maintain suspend
/linux/Documentation/scsi/
H A DChangeLog.lpfc108 waking up the els_tmo handler un-necessarily. The thread was
159 * Added code to prevent waking up worker thread after the exit of
/linux/Documentation/
H A Dmemory-barriers.txt2151 Sleeping and waking on an event flagged in global data can be viewed as an