Home
last modified time | relevance | path

Searched refs:waiting (Results 1 – 195 of 195) sorted by relevance

/linux-4.4.14/drivers/isdn/gigaset/
Dproc.c43 cs->waiting = 1; in set_cidmode()
46 cs->waiting = 0; in set_cidmode()
52 wait_event(cs->waitqueue, !cs->waiting); in set_cidmode()
Dcommon.c526 at_state->waiting = 0; in gigaset_at_init()
708 cs->waiting = 0; in gigaset_initcs()
861 if (cs->waiting) { in cleanup_cs()
863 cs->waiting = 0; in cleanup_cs()
898 cs->waiting = 1; in gigaset_start()
901 cs->waiting = 0; in gigaset_start()
906 wait_event(cs->waitqueue, !cs->waiting); in gigaset_start()
936 cs->waiting = 1; in gigaset_shutdown()
942 wait_event(cs->waitqueue, !cs->waiting); in gigaset_shutdown()
963 cs->waiting = 1; in gigaset_stop()
[all …]
Dinterface.c42 cs->waiting = 1; in if_lock()
45 cs->waiting = 0; in if_lock()
50 wait_event(cs->waitqueue, !cs->waiting); in if_lock()
76 cs->waiting = 1; in if_version()
79 cs->waiting = 0; in if_version()
84 wait_event(cs->waitqueue, !cs->waiting); in if_version()
Dev-layer.c922 cs->waiting = 0; in do_start()
942 cs->waiting = 0; in finish_shutdown()
1119 at_state->waiting = 1; in do_action()
1466 cs->waiting = 0; in do_action()
1478 cs->waiting = 0; in do_action()
1498 cs->waiting = 0; in do_action()
1574 if (at_state->waiting) in process_event()
1619 at_state->waiting = 0; in process_event()
Dgigaset.h335 int waiting; member
416 int waiting; member
/linux-4.4.14/drivers/media/v4l2-core/
Dv4l2-async.c67 list_for_each_entry(asd, &notifier->waiting, list) { in v4l2_async_belongs()
122 if (list_empty(&notifier->waiting) && notifier->complete) in v4l2_async_test_notify()
148 INIT_LIST_HEAD(&notifier->waiting); in v4l2_async_notifier_register()
166 list_add_tail(&asd->list, &notifier->waiting); in v4l2_async_notifier_register()
318 list_add(&sd->asd->list, &notifier->waiting); in v4l2_async_unregister_subdev()
/linux-4.4.14/drivers/scsi/
Dppa.c40 wait_queue_head_t *waiting; member
60 wake_up(dev->waiting); in got_it()
991 DECLARE_WAIT_QUEUE_HEAD_ONSTACK(waiting); in __ppa_attach()
1004 init_waitqueue_head(&waiting); in __ppa_attach()
1015 dev->waiting = &waiting; in __ppa_attach()
1016 prepare_to_wait(&waiting, &wait, TASK_UNINTERRUPTIBLE); in __ppa_attach()
1024 dev->waiting = NULL; in __ppa_attach()
1025 finish_wait(&waiting, &wait); in __ppa_attach()
1028 dev->waiting = NULL; in __ppa_attach()
1029 finish_wait(&waiting, &wait); in __ppa_attach()
Dimm.c46 wait_queue_head_t *waiting; member
69 wake_up(dev->waiting); in got_it()
1127 DECLARE_WAIT_QUEUE_HEAD_ONSTACK(waiting); in __imm_attach()
1133 init_waitqueue_head(&waiting); in __imm_attach()
1155 dev->waiting = &waiting; in __imm_attach()
1156 prepare_to_wait(&waiting, &wait, TASK_UNINTERRUPTIBLE); in __imm_attach()
1164 dev->waiting = NULL; in __imm_attach()
1165 finish_wait(&waiting, &wait); in __imm_attach()
1168 dev->waiting = NULL; in __imm_attach()
1169 finish_wait(&waiting, &wait); in __imm_attach()
Dst.h31 struct completion *waiting; member
Dosst.h637 struct completion *waiting; member
Dst.c526 if (SRpnt->waiting) in st_scsi_execute_end()
527 complete(SRpnt->waiting); in st_scsi_execute_end()
594 struct completion *waiting; in st_do_scsi() local
620 waiting = &STp->wait; in st_do_scsi()
621 init_completion(waiting); in st_do_scsi()
622 SRpnt->waiting = waiting; in st_do_scsi()
647 wait_for_completion(waiting); in st_do_scsi()
648 SRpnt->waiting = NULL; in st_do_scsi()
682 SRpnt->waiting = NULL; in write_behind_check()
Dhpsa_cmd.h429 struct completion *waiting; member
Dosst.c333 if (SRpnt->waiting) in osst_end_async()
334 complete(SRpnt->waiting); in osst_end_async()
435 struct completion *waiting; in osst_do_scsi() local
467 waiting = &STp->wait; in osst_do_scsi()
468 init_completion(waiting); in osst_do_scsi()
469 SRpnt->waiting = waiting; in osst_do_scsi()
489 wait_for_completion(waiting); in osst_do_scsi()
490 SRpnt->waiting = NULL; in osst_do_scsi()
523 STp->buffer->last_SRpnt->waiting = NULL; in osst_write_behind_check()
Dhpsa.c2634 c->waiting = &wait; in hpsa_scsi_do_simple_cmd_core()
6497 c->waiting = NULL; in hpsa_send_host_reset()
6780 complete(c->waiting); in finish_cmd()
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-class-scsi_tape16 Shows the total amount of time spent waiting for all I/O
23 To determine the amount of time spent waiting for other I/O
64 Shows the total amount of time in nanoseconds waiting for
95 Shows the total amount of time in nanoseconds waiting for
/linux-4.4.14/block/
Dblk-exec.c25 struct completion *waiting = rq->end_io_data; in blk_end_sync_rq() local
33 complete(waiting); in blk_end_sync_rq()
Dcfq-iosched.c479 CFQG_FLAG_FNS(waiting)
/linux-4.4.14/tools/perf/util/
Drun-command.c162 pid_t waiting = waitpid(pid, &status, 0); in wait_or_whine() local
164 if (waiting < 0) { in wait_or_whine()
171 if (waiting != pid) in wait_or_whine()
/linux-4.4.14/arch/arm/include/debug/
Dsamsung.S62 @ busy waiting for non fifo
81 @ idle waiting for non fifo
/linux-4.4.14/drivers/parport/
Dshare.c756 tmp->waiting = 0; in parport_register_device()
883 par_dev->waiting = 0; in parport_register_dev_model()
1135 if (dev->waiting & 1) { in parport_claim()
1136 dev->waiting = 0; in parport_claim()
1183 if (dev->waiting & 2 || dev->wakeup) { in parport_claim()
1185 if (test_and_set_bit(0, &dev->waiting) == 0) { in parport_claim()
1217 dev->waiting = 2; in parport_claim_or_block()
1236 if (dev->waiting) { in parport_claim_or_block()
1238 !dev->waiting); in parport_claim_or_block()
1259 dev->waiting = 0; in parport_claim_or_block()
[all …]
/linux-4.4.14/Documentation/scheduler/
Dcompletion.txt24 struct completion that tells the waiting threads of execution if they
36 struct completion, the waiting part through a call to one of the variants of
50 providing the wait queue to place tasks on for waiting and the flag for
119 to wait_for_completion() then the waiting side simply will continue
162 while waiting it will return -ERESTARTSYS; 0 otherwise.
191 variants, except for accounting waiting time as waiting on IO, which has
213 a thread starts waiting. This is achieved by the waiter "consuming"
Dsched-stats.txt52 8) sum of all time spent waiting to run by tasks on this processor (in
147 2) time spent waiting on a runqueue
/linux-4.4.14/drivers/sbus/char/
Dbbc_i2c.c128 bp->waiting = 1; in wait_for_pin()
144 bp->waiting = 0; in wait_for_pin()
277 if (bp->waiting && in bbc_i2c_interrupt()
316 bp->waiting = 0; in attach_one_i2c()
Dbbc_i2c.h62 volatile int waiting; member
/linux-4.4.14/Documentation/block/
Dstat.txt58 waited on this block device. If there are multiple I/O requests waiting,
80 on this block device. If there are multiple I/O requests waiting, this
82 number of requests waiting (see "read ticks" above for an example).
Drequest.txt79 struct completion *waiting D Can be used by driver to get signalled
Dcfq-iosched.txt225 Idling on a queue is primarily about waiting for the next request to come
246 of queues or the tree. So if there are 4 queues waiting for IO to dispatch
Dbiodoc.txt1026 the queue gets explicitly unplugged as part of waiting for completion on that
/linux-4.4.14/arch/x86/platform/uv/
Duv_nmi.c303 int last_k = 0, waiting = 0; in uv_nmi_wait_cpus() local
329 waiting = 0; in uv_nmi_wait_cpus()
330 } else if (++waiting > uv_nmi_wait_count) in uv_nmi_wait_cpus()
334 if (waiting && (n - k) == 1 && in uv_nmi_wait_cpus()
/linux-4.4.14/kernel/locking/
Drwsem-xadd.c440 bool waiting = true; /* any queued threads before us */ in rwsem_down_write_failed() local
461 waiting = false; in rwsem_down_write_failed()
466 if (waiting) { in rwsem_down_write_failed()
/linux-4.4.14/drivers/gpu/drm/savage/
Dsavage_state.c50 dev_priv->waiting = 1; in savage_emit_clip_rect_s3d()
76 dev_priv->waiting = 1; in savage_emit_clip_rect_s4()
253 dev_priv->waiting = 1; in savage_dispatch_state()
359 if (S3_SAVAGE3D_SERIES(dev_priv->chipset) && dev_priv->waiting) { in savage_dispatch_dma_prim()
368 dev_priv->waiting = 0; in savage_dispatch_dma_prim()
609 if (S3_SAVAGE3D_SERIES(dev_priv->chipset) && dev_priv->waiting) { in savage_dispatch_dma_idx()
618 dev_priv->waiting = 0; in savage_dispatch_dma_idx()
1039 dev_priv->waiting = 1; in savage_bci_cmdbuf()
Dsavage_drv.h186 unsigned int waiting; member
/linux-4.4.14/Documentation/accounting/
Dtaskstats-struct.txt100 /* Delay waiting for cpu, while runnable
108 /* Delay waiting for synchronous block I/O to complete
114 /* Delay waiting for page fault I/O (swap in only) */
177 /* Delay waiting for memory reclaim */
Ddelay-accounting.txt11 a) waiting for a CPU (while being runnable)
49 experienced by the task waiting for the corresponding resource
/linux-4.4.14/drivers/block/drbd/
Ddrbd_interval.h13 int waiting:1; /* someone is waiting for this to complete */ member
Ddrbd_req.c70 req->i.waiting = false; in drbd_req_new()
93 if (i->waiting) in drbd_remove_request_interval()
305 if (req->i.waiting) in drbd_req_complete()
530 if (req->i.waiting) in mod_rq_state()
810 if (req->i.waiting) in __req_mod()
990 i->waiting = true; in complete_conflicting_writes()
Ddrbd_main.c3736 i->waiting = true; in drbd_wait_misc()
Ddrbd_receiver.c1489 if (i->waiting) in drbd_remove_epoch_entry_interval()
/linux-4.4.14/include/media/
Dv4l2-async.h82 struct list_head waiting; member
/linux-4.4.14/Documentation/
Drobust-futex-ABI.txt22 call, and handles contested locking by maintaining a list of waiting
24 waiting on a particular futex, and waking up the next waiter on a
32 waiting on the same locks.
80 waiting for a lock on a threads exit if that next thread used the futex
88 indicating their holder died, and wakeup the next thread waiting for
164 they were waiting, and bit 30 is set by the kernel to indicate that the
Dfutex-requeue-pi.txt16 pthread_cond_broadcast() must resort to waking all the tasks waiting
89 is necessary for both the requeue code, as well as the waiting code,
112 possibly wake the waiting tasks. Internally, this system call is
Dvolatile-considered-harmful.txt34 want to play with that data will be waiting on the lock. The spinlock
59 when the processor is busy-waiting on the value of a variable. The right
68 waiting is generally an anti-social act to begin with.
Dkselftest.txt7 On some systems, hot-plug tests could hang forever waiting for cpu and
Dhwspinlock.txt70 waiting for it to be released, but give up when the timeout elapses.
82 waiting for it to be released, but give up when the timeout elapses.
94 waiting for it to be released, but give up when the timeout elapses.
Drpmsg.txt121 return -ENOMEM without waiting until one becomes available.
135 return -ENOMEM without waiting until one becomes available.
150 return -ENOMEM without waiting until one becomes available.
Dmd-cluster.txt90 or other events that happened while waiting for the TOKEN may have made
Dparport.txt174 spintime The number of microseconds to busy-loop while waiting
Dcrc32.txt164 immediately, without waiting for the previous loop iteration.
Dparport-lowlevel.txt595 1 timed out while waiting (35ms elapsed)
621 1 timed out while waiting (usec microseconds have elapsed)
Dworkqueue.txt150 pressure. Else it is possible that the worker-pool deadlocks waiting
Dmemory-barriers.txt1831 signal whilst asleep waiting for the lock to become available. Failed
1946 interaction between two pieces of data: the task state of the task waiting for
2227 Consider, for example, the R/W semaphore slow path. Here a waiting process is
2229 the semaphore's list of waiting processes:
Dmd.txt294 clean, but writes are blocked waiting for 'active' to be written.
Ddevices.txt3327 Under no circumstances should an application hold a lock while waiting
Dkernel-parameters.txt2629 waiting for the ACK, so if this is set too high
/linux-4.4.14/arch/arm/mach-pxa/
Dsleep.S33 20: b 20b @ waiting for sleep
171 20: b 20b @ loop waiting for sleep
/linux-4.4.14/drivers/gpu/drm/nouveau/include/nvkm/subdev/
Dclk.h85 atomic_t waiting; member
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/subdev/clk/
Dbase.c210 if (!atomic_xchg(&clk->waiting, 0)) in nvkm_pstate_work()
243 atomic_set(&clk->waiting, 1); in nvkm_pstate_calc()
246 wait_event(clk->wait, !atomic_read(&clk->waiting)); in nvkm_pstate_calc()
572 atomic_set(&clk->waiting, 0); in nvkm_clk_ctor()
/linux-4.4.14/drivers/net/ethernet/cavium/liquidio/
Docteon_console.c450 console->waiting = 0; in octeon_console_handle_result()
511 if (console->waiting) { in check_console()
591 console->waiting = 0; in octeon_add_console()
Docteon_device.h181 u32 waiting; member
/linux-4.4.14/drivers/gpu/drm/
Ddrm_dma.c133 buf->waiting = 0; in drm_legacy_free_buffer()
Ddrm_bufs.c700 buf->waiting = 0; in drm_legacy_addbufs_agp()
898 buf->waiting = 0; in drm_legacy_addbufs_pci()
1063 buf->waiting = 0; in drm_legacy_addbufs_sg()
/linux-4.4.14/arch/cris/
DKconfig.debug23 didn't before). The kernel halts when it boots, waiting for gdb if
/linux-4.4.14/Documentation/networking/
Dspider_net.txt29 and is waiting to be emptied and processed by the OS. A "not-in-use"
132 which, from the OS point of view, is empty; the OS will be waiting for
135 is a potential deadlock, with the OS waiting for one descr to fill,
136 while the hardware is waiting for a different set of descrs to become
158 as explained in the last section. The OS is waiting for descr 255 to
Dmac80211-injection.txt28 IEEE80211_RADIOTAP_F_TX_NOACK: frame should be sent without waiting for
Doperstates.txt61 Interface is L1 up, but waiting for an external event, f.e. for a
157 waiting for operstate to go IF_OPER_UP/IF_OPER_UNKNOWN before
Dtcp-thin.txt13 waiting for long timeouts.
Dcxacru.txt65 "waiting"
Ddriver.txt72 This error can deadlock sockets waiting for send buffer room
Dnetdevices.txt104 NAPI_STATE_SCHED napi->state bit, waiting for all pending
Dbatman-adv.txt28 The module is now waiting for activation. You must add some in-
DPLIP.txt74 the PLIP driver would constantly poll the parallel port for data waiting,
Dpktgen.txt42 the TX ring might just be waiting for cleanup.
Drds.txt223 Messages waiting in the receive queue on the receiving socket
Dphy.txt48 time, so it is safe for them to block, waiting for an interrupt to signal
Drxrpc.txt250 Any messages waiting in the receive queue for that call will be discarded.
662 Any packets waiting in the socket's receive queue will be discarded if
Dtimestamping.txt325 block waiting on a timestamp, use poll or select. poll() will return
Dip-sysctl.txt211 packet for the flow is waiting in Qdisc queues or device transmit
Dbonding.txt2518 case). If there are slave interfaces waiting for the updelay timeout
/linux-4.4.14/Documentation/RCU/
Dtrace.txt136 grace-period processing that they are in (new, waiting for
137 grace period to start, waiting for grace period to end, ready
152 waiting on the current grace period.
156 thus waiting to be invoked. Note that callbacks in
214 "W" The kernel thread is waiting because there is no work
217 "O" The kernel thread is waiting because it has been
400 o "qsp" is the number of times that the RCU was waiting for a
471 "W" The kernel thread is waiting because there is no work
535 o "qlen" is the number of RCU callbacks currently waiting either
536 for an RCU grace period or waiting to be invoked. This is the
Drcubarrier.txt73 We instead need the rcu_barrier() primitive. Rather than waiting for
78 without waiting for a grace period to elapse.
Dchecklist.txt246 those waiting for a grace period to elapse. Enforce a
DwhatisRCU.txt1014 short of memory). In contrast, if blocking waiting
DRTFP.txt70 simplest deferred-free technique: simply waiting a fixed amount of time
/linux-4.4.14/include/drm/
Ddrm_legacy.h57 __volatile__ int waiting; /**< On kernel DMA queue */ member
/linux-4.4.14/drivers/mmc/host/
Djz4740_mmc.c136 unsigned long waiting; member
431 set_bit(0, &host->waiting); in jz4740_mmc_poll_irq()
599 if (!test_and_clear_bit(0, &host->waiting)) in jz4740_mmc_timeout()
797 if (test_and_clear_bit(0, &host->waiting)) { in jz_mmc_irq()
854 set_bit(0, &host->waiting); in jz4740_mmc_request()
/linux-4.4.14/drivers/net/wan/
Dsdla.c437 int ret, waiting, len; in sdla_cmd() local
461 waiting = 1; in sdla_cmd()
463 while (waiting && time_before_eq(jiffies, jiffs)) in sdla_cmd()
465 if (waiting++ % 3) in sdla_cmd()
469 waiting = ((volatile int)(cmd_buf->opp_flag)); in sdla_cmd()
474 if (!waiting) in sdla_cmd()
/linux-4.4.14/Documentation/locking/
Dlockstat.txt49 total - total time we spend waiting on this lock
50 avg - average time spent waiting on this lock
Dmutex-design.txt72 waiting to spin on mutex owner, only to go directly to slowpath upon
82 task and busy-waiting for a few cycles instead of immediately sleeping,
Drt-mutex-design.txt39 Now there's no way of knowing how long A will be sleeping waiting for C
104 waiter is sometimes used in reference to the task that is waiting
109 top waiter - The highest priority process waiting on a specific mutex.
111 top pi waiter - The highest priority process waiting on one of the mutexes
223 is waiting on a mutex that is owned by the task. So if the task has
372 task's own normal priority, or if a process of a higher priority is waiting on
396 always contains the highest priority task that is waiting on a mutex owned
448 task that owns a mutex that this current task is waiting on. A priority chain
673 priority process currently waiting on this mutex, then we remove the
Dspinlocks.txt123 lock will obviously never be released (because the interrupt is waiting
Dww-mutex-design.txt14 become ready. If you think about this in terms of waiting on a buffer
/linux-4.4.14/Documentation/devicetree/bindings/clock/ti/
Dinterface.txt18 capability for waiting clock to be ready
/linux-4.4.14/Documentation/usb/
Ddwc3.txt39 handles the remaining EP work which might sleep such as waiting
/linux-4.4.14/drivers/block/
Dcciss_cmd.h210 struct completion *waiting; member
Dcciss.c1544 c->waiting = &wait; in cciss_passthru()
1672 c->waiting = &wait; in cciss_bigpassthru()
2700 c->waiting = NULL; in cciss_send_reset()
2806 c->waiting = &wait; in sendcmd_withirq_core()
3494 complete(c->waiting); in finish_cmd()
Dcciss_scsi.c944 c->waiting = &wait; in cciss_scsi_do_simple_cmd()
/linux-4.4.14/arch/arm/mach-sa1100/
Dsleep.S143 20: b 20b @ loop waiting for sleep
/linux-4.4.14/drivers/scsi/libsas/
Dsas_ata.c590 struct completion *waiting; in sas_ata_task_abort() local
607 waiting = qc->private_data; in sas_ata_task_abort()
608 complete(waiting); in sas_ata_task_abort()
/linux-4.4.14/Documentation/filesystems/
Dfuse.txt133 'waiting'
135 The number of requests which are waiting to be transferred to
137 no filesystem activity and 'waiting' is non-zero, then the
143 connection. This means that all waiting requests will be aborted an
Docfs2.txt103 journal_async_commit Commit block can be written to disk without waiting
Ddirectory-locking79 waiting on another non-directory lock with a larger address. Therefore
Dxfs-delayed-logging-design.txt462 complete before waiting on the one we need to complete. We do this
525 available when required, then the regrant code will sleep waiting for it.
554 a CIL push triggered by a log force, only that there is no waiting for the
666 checkpoints and needs to block waiting for checkpoints to complete their commit
672 events they are waiting for are different. The checkpoint commit record
Dproc.txt323 blkio_ticks time spent waiting for block IO
896 Dirty: Memory which is waiting to get written back to the disk
1299 - iowait: waiting for I/O to complete
1325 waiting for I/O to complete.
Dcoda.txt231 when no messages are waiting or being processed.
364 file descriptor for the device. The process P is kept waiting on an
372 message arrival. The process P is kept waiting on a KernelEvent
Dspufs.txt338 0x08 SPU is waiting for a channel.
Dpath-lookup.txt114 new list before waiting for a grace period, this can result in a concurrent RCU
Dext4.txt142 journal_async_commit Commit block can be written to disk without waiting
Dvfs.txt539 complete. While waiting ->sync_page (if defined) will be called on
1048 waiting to explore behind a 'mountpoint' whilst letting the daemon go
/linux-4.4.14/Documentation/i2c/
Di2c-stub59 If your target driver polls some byte or word waiting for it to change, the
/linux-4.4.14/Documentation/sysctl/
Dnet.txt71 Approximate time in us to busy loop waiting for packets on the device queue.
82 Approximate time in us to busy loop waiting for events.
239 received queue (bytes waiting for applications to read) the state and the uid
Dkernel.txt234 parallel, but that no waiting will take place (i.e. the collecting
/linux-4.4.14/Documentation/cgroups/
Dblkio-controller.txt225 - Total amount of time the IOs for this cgroup spent waiting in the
228 measure of total time the cgroup spent waiting but rather a measure of
230 this metric does not include the time spent waiting for service once
261 waiting in the scheduler queue. This is in nanoseconds. If this is
262 read when the cgroup is in a waiting (for timeslice) state, the stat
Dfreezer-subsystem.txt22 blocked, or ignored it can be seen by waiting or ptracing parent tasks.
Dcpusets.txt532 CPU Y without waiting task A on CPU X.
548 on the next tick. For some applications in special situation, waiting
Dmemory.txt496 dirty - # of bytes that are waiting to get written back to the disk.
/linux-4.4.14/Documentation/scsi/
Dst.txt97 skip waiting.
175 2. io_ns - The amount of time spent waiting (in nanoseconds) for all I/O
184 6. read_ns - The amount of time (in nanoseconds) spent waiting for read
188 9. write_ns - The amount of time (in nanoseconds) spent waiting for write
577 the driver is waiting. With the command 'ps -l' you can see the state
579 waiting for something. The field WCHAN tells where the driver is
580 waiting. If you have the current System.map in the correct place (in
DChangeLog.sym53c8xx_2118 threads. A timer is also used to prevent from waiting indefinitely.
DChangeLog.1992-1997167 * st.c: Perform some waiting operations with interrupts off.
502 Do not use waiting loops - use up and down mechanism as long
551 all been waiting for. It fixes a problem whereby the driver
832 processes waiting.
1235 * (Throughout): Use request.sem instead of request.waiting.
1980 (allocate_request, request_queueable): Init request.waiting to NULL if
DChangeLog.ncr53c8xx443 inserting these commands into the waiting list. The waiting list
DChangeLog.megaraid_sas437 waiting for depending on cmd completion from isr path.
DChangeLog.megaraid426 ii. Display elapsed time (countdown) while waiting for FW to boot.
DChangeLog.lpfc29 if we timed out waiting for command to complete after abort was
390 waiting on a semaphore and "modprobe -r lpfc" is not always
/linux-4.4.14/Documentation/vm/
Dpage_migration135 so will enable access for user space processes not already waiting for
139 Processes waiting on the page lock will redo their page faults
Duserfaultfd.txt97 aren't waiting for userfaults (i.e. network bound) can keep running in
/linux-4.4.14/fs/squashfs/
DKconfig78 machines due to waiting on decompressor availability.
92 machines due to waiting on decompressor availability.
/linux-4.4.14/Documentation/device-mapper/
Ddm-io.txt70 always available in order to avoid unnecessary waiting while performing I/O.
Dlog-writes.txt19 make it easier to detect improper waiting/flushing.
Dcache-policies.txt34 waiting for the cache and another two for those in the cache (a set for
/linux-4.4.14/drivers/staging/lustre/lustre/osc/
Dosc_cache.c2624 struct osc_extent *waiting = NULL; in osc_cache_truncate_start() local
2652 waiting = osc_extent_get(ext); in osc_cache_truncate_start()
2721 if (waiting != NULL) { in osc_cache_truncate_start()
2726 rc = osc_extent_wait(env, waiting, OES_INV); in osc_cache_truncate_start()
2728 OSC_EXTENT_DUMP(D_CACHE, waiting, "error: %d.\n", rc); in osc_cache_truncate_start()
2730 osc_extent_put(env, waiting); in osc_cache_truncate_start()
2731 waiting = NULL; in osc_cache_truncate_start()
/linux-4.4.14/net/irda/
DKconfig75 start backing-off before sending another RR frame, waiting longer
/linux-4.4.14/Documentation/x86/x86_64/
Dmachinecheck74 exception. 0 to disable waiting for other CPUs.
/linux-4.4.14/Documentation/dmaengine/
Ddmatest.txt51 waiting is disabled.
Dprovider.txt283 transaction descriptor to a pending queue, waiting
/linux-4.4.14/Documentation/misc-devices/mei/
Dmei-client-bus.txt50 In order for drivers to be notified of pending events waiting for them (e.g.
/linux-4.4.14/drivers/scsi/aic7xxx/
Daic79xx.seq85 * If we have completions stalled waiting for the qfreeze
249 * If there are more commands waiting to be dma'ed
259 * bother waiting for another command to complete.
364 * into the waiting for selection queue. Otherwise
369 * SCB can be queued to the waiting for selection
400 * Append SCB to the tail of the waiting for
420 * a MK_MESSAGE SCB waiting to enter the queue.
656 * Dequeue all SCBs sent from the waiting queue
657 * Requeue all SCBs *not* sent to the tail of the waiting queue
751 * Requeue any SCBs not sent, to the tail of the waiting Q.
[all …]
Daic7xxx.seq51 * A few words on the waiting SCB list:
59 * create yet another SCB waiting for selection. The solution used here is to
147 * Start the first entry on the waiting SCB list.
429 * After the selection, remove this SCB from the "waiting SCB"
Daic79xx.reg4049 * the waiting for selection list until the
/linux-4.4.14/drivers/infiniband/hw/nes/
Dnes_verbs.c114 cqp_request->waiting = 1; in nes_alloc_mw()
177 cqp_request->waiting = 1; in nes_dealloc_mw()
307 cqp_request->waiting = 1; in alloc_fast_reg_mr()
1322 cqp_request->waiting = 1; in nes_create_qp()
1640 cqp_request->waiting = 1; in nes_create_cq()
1799 cqp_request->waiting = 1; in nes_destroy_cq()
1937 cqp_request->waiting = 1; in nes_reg_mr()
2676 cqp_request->waiting = 1; in nes_dereg_mr()
2860 cqp_request->waiting = 1; in nes_hw_modify_qp()
2862 cqp_request->waiting = 0; in nes_hw_modify_qp()
Dnes_utils.c585 cqp_request->waiting = 0; in nes_get_cqp_request()
658 cqp_request->waiting, atomic_read(&cqp_request->refcount)); in nes_post_cqp_request()
Dnes_hw.c3057 if (cqp_request->waiting) { in nes_cqp_ce_handler()
3788 cqp_request->waiting = 1; in nes_manage_apbvt()
3848 cqp_request->waiting = 0; in nes_manage_arp_cache()
3896 cqp_request->waiting = 1; in flush_wqes()
3899 cqp_request->waiting = 0; in flush_wqes()
Dnes_hw.h889 u8 waiting; member
Dnes.c337 cqp_request->waiting = 0; in nes_rem_ref()
/linux-4.4.14/Documentation/video4linux/
Dvideobuf310 waiting for it.
314 - Mark the buffer as done and wake up the process waiting for it.
323 process is waiting on it. That test can be done by examining the buffer's
Dv4l2-framework.txt736 processes to access the device node while the first process is waiting for
/linux-4.4.14/include/linux/
Dparport.h156 unsigned long waiting; /* long req'd for set_bit --RR */ member
/linux-4.4.14/arch/mn10300/kernel/
Dhead.S400 # now sleep waiting for further instructions
/linux-4.4.14/Documentation/filesystems/pohmelfs/
Ddesign_notes.txt44 caller sleeps waiting for it. Thus, it is possible to issue multiple read commands to different
/linux-4.4.14/Documentation/powerpc/
Dfirmware-assisted-dump.txt98 we check to see if an active dump is waiting for us. If yes
106 If there is no waiting dump data, then only the memory required
/linux-4.4.14/Documentation/filesystems/caching/
Dobject.txt247 Any child objects waiting on this one are given CPU time so that they too
253 The object comes to this state if it was waiting on its parent in
Doperations.txt174 necessary (the object might have died whilst the thread was waiting).
Dnetfs-api.txt580 anyone waiting for that bit will be woken up.
/linux-4.4.14/drivers/char/ipmi/
Dipmi_ssif.c556 bool waiting; in retry_timeout() local
562 waiting = ssif_info->waiting_alert; in retry_timeout()
566 if (waiting) in retry_timeout()
/linux-4.4.14/fs/fuse/
Dcuse.c576 static DEVICE_ATTR(waiting, 0400, cuse_class_waiting_show, NULL);
/linux-4.4.14/Documentation/arm/
Dtcm.txt55 the CPU and then we hang inside ITCM waiting for an
/linux-4.4.14/Documentation/PCI/
Dpci-error-recovery.txt33 waiting for some i/o-space register to change, when it never will.
131 a chance to cleanup, waiting for pending stuff (timers, whatever, etc...)
169 >>> recovery implementation (e.g. waiting for all notification threads
/linux-4.4.14/Documentation/aoe/
Daoe.txt43 "cat /dev/etherd/err" blocks, waiting for error diagnostic output,
/linux-4.4.14/Documentation/input/
Dntrig.txt90 contact immediately overrides the waiting period and leads to activation.
/linux-4.4.14/Documentation/nfc/
Dnfc-hci.txt21 context blocks waiting for response) or asynchronously (the response is returned
233 waiting command execution. Response processing involves invoking the completion
/linux-4.4.14/fs/exofs/
Dore.c340 struct completion *waiting = p; in _sync_done() local
342 complete(waiting); in _sync_done()
/linux-4.4.14/Documentation/power/
Dsuspend-and-interrupts.txt98 system sleep state that works by idling all of the processors and waiting for
Dsuspend-and-cpuhotplug.txt268 it will now start waiting on the frozen userspace in the
Dfreezing-of-tasks.txt138 user threads and then waiting for a sync is practically one of the easier
/linux-4.4.14/drivers/lightnvm/
Drrpc.c250 struct completion *waiting = bio->bi_private; in rrpc_end_sync_bio() local
255 complete(waiting); in rrpc_end_sync_bio()
/linux-4.4.14/Documentation/isdn/
DREADME.hysdn132 1007 Timeout waiting for card ready during boot
DINTERFACE504 If ICALLW is signalled the incoming call is a waiting call without
/linux-4.4.14/drivers/gpu/drm/i915/
Di915_gpu_error.c301 err_printf(m, " waiting: %s\n", yesno(ring->waiting)); in i915_ring_error_state()
892 ering->waiting = waitqueue_active(&ring->irq_queue); in i915_record_ring_state()
Di915_drv.h529 bool waiting; member
/linux-4.4.14/drivers/scsi/lpfc/
Dlpfc_bsg.c61 int waiting; member
1255 evt->waiting = 1; in lpfc_bsg_hba_set_event()
2631 evt->waiting = 1; in lpfcdiag_loop_get_xri()
2647 evt->waiting = 0; in lpfcdiag_loop_get_xri()
3209 evt->waiting = 1; in lpfc_bsg_diag_loopback_run()
3214 evt->waiting = 0; in lpfc_bsg_diag_loopback_run()
/linux-4.4.14/Documentation/arm/SA1100/
DAssabet237 Then, rebooting the Assabet is just a matter of waiting for the login prompt.
/linux-4.4.14/drivers/scsi/csiostor/
Dcsio_hw.c873 int waiting = FW_CMD_HELLO_TIMEOUT; in csio_do_hello() local
888 waiting -= 50; in csio_do_hello()
898 if (waiting <= 0) { in csio_do_hello()
/linux-4.4.14/Documentation/filesystems/nfs/
Drpc-cache.txt156 select or poll for read will block waiting for another request to be
/linux-4.4.14/Documentation/hwmon/
Dlm90269 two transactions will typically mean twice as much delay waiting for
/linux-4.4.14/Documentation/virtual/kvm/
Dmsr.txt192 up all processes waiting for APFs and no individual type 2 APFs
Dapi.txt1052 is waiting for an interrupt [x86]
/linux-4.4.14/net/netfilter/ipvs/
DKconfig246 the idle server, instead of waiting for a fast one. When there
/linux-4.4.14/arch/powerpc/xmon/
Dxmon.c445 goto waiting; in xmon_core()
475 waiting: in xmon_core()
/linux-4.4.14/Documentation/target/
Dtcmu-design.txt137 cmd_tail, the ring is empty -- no commands are currently waiting to be
/linux-4.4.14/Documentation/gpio/
Dconsumer.txt198 SPI. Commands to read or write those GPIO values require waiting to get to the
Dgpio-legacy.txt198 or SPI. Commands to read or write those GPIO values require waiting to
/linux-4.4.14/scripts/
Dspelling.txt1056 wating||waiting
/linux-4.4.14/Documentation/hid/
Dhid-transport.txt77 not perform any synchronous operations like waiting for acknowledgements or
/linux-4.4.14/Documentation/rapidio/
Drapidio.txt129 and are waiting for enumeration to be completed.
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/engine/ce/fuc/
Dcom.fuc262 // is there a channel waiting to be loaded?
/linux-4.4.14/drivers/net/ethernet/chelsio/cxgb4/
Dt4_hw.c5817 int waiting = FW_CMD_HELLO_TIMEOUT; in t4_fw_hello() local
5830 waiting -= 50; in t4_fw_hello()
5840 if (waiting <= 0) { in t4_fw_hello()
/linux-4.4.14/drivers/block/mtip32xx/
Dmtip32xx.c579 struct completion *waiting = command->comp_data; in mtip_completion() local
586 complete(waiting); in mtip_completion()
/linux-4.4.14/net/sched/
DKconfig51 scheduling algorithm. This algorithm classifies the waiting packets
/linux-4.4.14/drivers/ata/
Dlibata-core.c1526 struct completion *waiting = qc->private_data; in ata_qc_complete_internal() local
1528 complete(waiting); in ata_qc_complete_internal()
/linux-4.4.14/Documentation/development-process/
D2.Process94 worse; the pile of changes waiting for the next merge window will grow
/linux-4.4.14/arch/arm/mm/
DKconfig953 drain and waiting for all buffers empty.
/linux-4.4.14/init/
DKconfig440 Collect information on time spent by a task waiting for system
1878 without waiting for anyone to stop using it (using the -f option to
/linux-4.4.14/Documentation/filesystems/cifs/
DCHANGES440 waiting on an SMB response) in SendReceive when session dies but
/linux-4.4.14/Documentation/cdrom/
Dcdrom-standard.tex343 course waiting for the device should not use processor time.
/linux-4.4.14/arch/arm/
DKconfig1187 continuously polls a memory location waiting to observe an update.
/linux-4.4.14/Documentation/sound/alsa/
DALSA-Configuration.txt1814 sleep_interval - How long to sleep when waiting for reply
/linux-4.4.14/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt721 appear to hang. In reality, it's waiting for a telnet to connect, at