| /linux/tools/verification/models/sched/ |
| H A D | sssw.dot | 9 {node [shape = circle] "sleeping"}; 14 "runnable" -> "sleeping" [ label = "sched_switch_blocking" ]; 23 "sleepable" -> "sleeping" [ label = "sched_switch_suspend\nsched_switch_blocking" ]; 24 "sleeping" [label = "sleeping"]; 25 "sleeping" -> "runnable" [ label = "sched_wakeup" ];
|
| /linux/kernel/trace/rv/monitors/sssw/ |
| H A D | Kconfig | 10 Monitor to ensure sched_set_state to sleepable leads to sleeping and 11 sleeping tasks require wakeup.
|
| /linux/drivers/macintosh/ |
| H A D | via-pmu-backlight.c | 23 static int sleeping, uses_pmu_bl; variable 104 if (!sleeping) in pmu_backlight_update_status() 122 sleeping = sleep; in pmu_backlight_set_sleep()
|
| H A D | mediabay.c | 65 int sleeping; member 545 if (!media_bays[i].sleeping) in media_bay_task() 587 bay->sleeping = 0; in media_bay_attach() 622 bay->sleeping = 1; in media_bay_suspend() 660 bay->sleeping = 0; in media_bay_resume()
|
| /linux/Documentation/scheduler/ |
| H A D | sched-eevdf.rst | 24 There are ongoing discussions on how to manage lag, especially for sleeping 27 by sleeping briefly to reset their negative lag: when a task sleeps, it 29 lag to decay over VRT. Hence, long-sleeping tasks eventually have their lag
|
| H A D | sched-arch.rst | 63 sleeping idle functions.
|
| /linux/Documentation/accounting/ |
| H A D | cgroupstats.rst | 29 sleeping 1, blocked 0, running 1, stopped 0, uninterruptible 0 31 sleeping 155, blocked 0, running 1, stopped 0, uninterruptible 2
|
| /linux/drivers/media/dvb-frontends/ |
| H A D | rtl2830_priv.h | 25 bool sleeping; member
|
| H A D | rtl2832_priv.h | 31 bool sleeping; member
|
| /linux/kernel/ |
| H A D | workqueue_internal.h | 38 int sleeping; /* S: is worker sleeping? */ member
|
| /linux/Documentation/locking/ |
| H A D | mutex-design.rst | 15 or similar theoretical text books. Mutexes are sleeping locks which 57 for sleeping lock implementation. An important feature of the customized 71 task and busy-waiting for a few cycles instead of immediately sleeping, 104 Mutexes - and most other sleeping locks like rwsems - do not provide an
|
| /linux/drivers/firmware/arm_scmi/transports/ |
| H A D | Kconfig | 58 mode, avoiding any kind of sleeping behaviour for selected 115 mode, avoiding any kind of sleeping behaviour for selected
|
| /linux/drivers/net/ethernet/apple/ |
| H A D | bmac.c | 77 int sleeping; member 469 bp->sleeping = 1; in bmac_suspend() 915 if (bp->sleeping) in bmac_set_multicast() 1148 bp->sleeping = 0; in bmac_reset_and_enable() 1337 bp->sleeping = 1; in bmac_close() 1384 if (bp->sleeping) in bmac_start()
|
| /linux/arch/arm64/boot/dts/qcom/ |
| H A D | msm8916-motorola-common.dtsi | 61 syna,nosleep-mode = <1>; /* Allow sleeping */
|
| H A D | msm8916-longcheer-l8150.dts | 245 syna,nosleep-mode = <1>; /* Allow sleeping */
|
| H A D | msm8916-huawei-g7.dts | 187 syna,nosleep-mode = <1>; /* Allow sleeping */
|
| /linux/drivers/gpu/drm/i915/ |
| H A D | Kconfig.profile | 96 Before sleeping waiting for a request (GPU operation) to complete, 113 By stopping submission and sleeping for a short time before resetting
|
| /linux/drivers/net/ethernet/chelsio/cxgb3/ |
| H A D | sge.c | 2253 unsigned int sleeping) in check_ring_db() argument 2255 if (sleeping & F_RSPD_TXQ0_GTS) { in check_ring_db() 2266 if (sleeping & F_RSPD_TXQ1_GTS) { in check_ring_db() 2328 unsigned int sleeping = 0; in process_responses() local 2407 sleeping |= flags & RSPD_GTS_MASK; in process_responses() 2449 if (sleeping) in process_responses() 2450 check_ring_db(adap, qs, sleeping); in process_responses() 2522 unsigned int sleeping = 0; in process_pure_responses() local 2536 sleeping |= flags & RSPD_GTS_MASK; in process_pure_responses() 2550 if (sleeping) in process_pure_responses() [all …]
|
| /linux/Documentation/usb/ |
| H A D | dwc3.rst | 39 sleeping is handed over to the Thread. The event is saved in an
|
| /linux/Documentation/virt/kvm/ |
| H A D | vcpu-requests.rst | 56 2) Waking a sleeping VCPU. Sleeping VCPUs are VCPU threads outside guest 61 sleeping, then there is nothing to do. 153 from VCPUs running in guest mode. That is, sleeping VCPUs do not need 162 If, for example, the VCPU is sleeping, so no IPI is necessary, then
|
| /linux/Documentation/userspace-api/media/ |
| H A D | gen-errors.rst | 24 device is sleeping and ioctl is performed to query statistics. It
|
| /linux/arch/arm/mach-pxa/ |
| H A D | sleep.S | 66 @ Intel PXA270 Specification Update notes problems sleeping
|
| /linux/Documentation/userspace-api/ |
| H A D | futex2.rst | 58 - A signal was sent to the sleeping task, returning ``-ERESTARTSYS``.
|
| /linux/Documentation/livepatch/ |
| H A D | livepatch.rst | 97 1. The first and most effective approach is stack checking of sleeping 108 a) Patching I/O-bound user tasks which are sleeping on an affected 163 are sleeping in (/proc/<pid>/stack may help here). Removal (rmmod) of patch 165 guaranteed there is no task sleeping in such module. It implies unbounded
|
| /linux/drivers/net/wireless/ath/ath9k/ |
| H A D | channel.c | 1584 if (an->sleeping == !!avp->noa.absent) in ath9k_p2p_ps_timer() 1587 an->sleeping = avp->noa.absent; in ath9k_p2p_ps_timer() 1588 if (an->sleeping) in ath9k_p2p_ps_timer()
|