Home
last modified time | relevance | path

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

1234567

/linux/tools/testing/selftests/arm64/abi/
H A Dtpidr2.c65 pid_t newpid, waiting, oldpid; in write_fork_read() local
94 waiting = waitpid(newpid, &status, 0); in write_fork_read()
96 if (waiting < 0) { in write_fork_read()
102 if (waiting != newpid) { in write_fork_read()
104 waiting, newpid); in write_fork_read()
144 pid_t parent, waiting; in write_clone_read()
184 waiting = waitpid(ret, &status, __WCLONE); in write_clone_read()
186 if (waiting < 0) { in write_clone_read()
192 if (waiting != ret) { in write_clone_read()
194 waiting); in write_clone_read()
145 pid_t parent, waiting; write_clone_read() local
[all...]
/linux/tools/testing/selftests/arm64/fp/
H A Dza-fork.c26 pid_t newpid, waiting; in fork_test_c() local
50 waiting = waitpid(newpid, &child_status, 0); in fork_test_c()
52 if (waiting < 0) { in fork_test_c()
58 if (waiting != newpid) { in fork_test_c()
/linux/Documentation/ABI/testing/
H A Dsysfs-devices-waiting_for_supplier10 or 1) reflects whether the device is waiting for one or more
14 A value of 0 means the device is not waiting for any suppliers
16 is waiting for one or more suppliers to be added before it can
H A 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
H A Dsysfs-bus-iio-distance-srf088 This setting limits the time the driver is waiting for a
H A Dsysfs-class-vduse31 (RW) The timeout (in seconds) for waiting for the control
/linux/tools/lib/subcmd/
H A Drun-command.c187 pid_t waiting = waitpid(cmd->pid, &status, block ? 0 : WNOHANG); in wait_or_whine()
189 if (!block && waiting == 0) in wait_or_whine()
192 if (waiting < 0 && errno == EINTR) in wait_or_whine()
196 if (waiting < 0) { in wait_or_whine()
202 } else if (waiting != cmd->pid) { in wait_or_whine()
266 pid_t waiting; in check_if_command_finished()
277 waiting = waitpid(cmd->pid, &status, WNOHANG); in run_command()
278 if (waiting == cmd->pid) { in run_command()
304 if (waiting < 0 && (errno == ECHILD || errno == ESRCH))
177 pid_t waiting = waitpid(cmd->pid, &status, block ? 0 : WNOHANG); wait_or_whine() local
/linux/Documentation/scheduler/
H A Dcompletion.rst22 until the result is actually needed, and both the waiting and the signalling
26 the Linux scheduler. The event the threads on the waitqueue are waiting for
39 - the waiting part through a call to one of the variants of wait_for_completion(),
43 Note that while initialization must happen first, the waiting and signaling
57 This provides the ->wait waitqueue to place tasks on for waiting (if any), and
122 must not return to a calling context until all activities (such as waiting
125 To emphasise this again: in particular when using some of the waiting API variants
164 to wait_for_completion() then the waiting side simply will continue
181 time depending on the nature of the activity they are waiting for, so in
206 This function marks the task TASK_INTERRUPTIBLE while it is waiting.
[all …]
/linux/drivers/scsi/
H A Dppa.c41 wait_queue_head_t *waiting; member
71 wake_up(dev->waiting); in got_it()
1038 DECLARE_WAIT_QUEUE_HEAD_ONSTACK(waiting); in __ppa_attach()
1051 init_waitqueue_head(&waiting); in __ppa_attach()
1069 dev->waiting = &waiting; in __ppa_attach()
1070 prepare_to_wait(&waiting, &wait, TASK_UNINTERRUPTIBLE); in __ppa_attach()
1078 dev->waiting = NULL; in __ppa_attach()
1079 finish_wait(&waiting, &wait); in __ppa_attach()
1082 dev->waiting = NULL; in __ppa_attach()
1083 finish_wait(&waiting, &wait); in __ppa_attach()
H A Dimm.c48 wait_queue_head_t *waiting; member
76 wake_up(dev->waiting); in got_it()
1153 DECLARE_WAIT_QUEUE_HEAD_ONSTACK(waiting); in __imm_attach()
1159 init_waitqueue_head(&waiting); in __imm_attach()
1187 dev->waiting = &waiting; in __imm_attach()
1188 prepare_to_wait(&waiting, &wait, TASK_UNINTERRUPTIBLE); in __imm_attach()
1196 dev->waiting = NULL; in __imm_attach()
1197 finish_wait(&waiting, &wait); in __imm_attach()
1200 dev->waiting = NULL; in __imm_attach()
1201 finish_wait(&waiting, &wait); in __imm_attach()
/linux/drivers/parport/
H A Dshare.c739 par_dev->waiting = 0; in parport_register_dev_model()
998 if (dev->waiting & 1) { in parport_claim()
999 dev->waiting = 0; in parport_claim()
1048 if (dev->waiting & 2 || dev->wakeup) { in parport_claim()
1050 if (test_and_set_bit(0, &dev->waiting) == 0) { in parport_claim()
1085 dev->waiting = 2; in parport_claim_or_block()
1107 if (dev->waiting) { in parport_claim_or_block()
1109 !dev->waiting); in parport_claim_or_block()
1128 dev->waiting = 0; in parport_claim_or_block()
1183 if (pd->waiting & 2) { /* sleeping in claim_or_block */ in parport_release()
/linux/arch/arm/include/debug/
H A Dsamsung.S63 @ busy waiting for non fifo
87 @ idle waiting for non fifo
/linux/drivers/sbus/char/
H A Dbbc_i2c.c130 bp->waiting = 1; in wait_for_pin()
146 bp->waiting = 0; in wait_for_pin()
279 if (bp->waiting && in bbc_i2c_interrupt()
318 bp->waiting = 0; in attach_one_i2c()
H A Dbbc_i2c.h62 volatile int waiting; member
/linux/Documentation/filesystems/fuse/
H A Dfuse-io-uring.rst39 pending requests waiting the request will be immediately submitted
62 | | [waiting for CQEs]
/linux/Documentation/block/
H A Dstat.rst79 waited on this block device. If there are multiple I/O requests waiting,
101 on this block device. If there are multiple I/O requests waiting, this
103 number of requests waiting (see "read ticks" above for an example).
/linux/drivers/block/drbd/
H A Ddrbd_interval.h14 unsigned int waiting:1; /* someone is waiting for completion */ member
/linux/Documentation/locking/
H A Dfutex-requeue-pi.rst17 pthread_cond_broadcast() must resort to waking all the tasks waiting
90 is necessary for both the requeue code, as well as the waiting code,
113 possibly wake the waiting tasks. Internally, this system call is
H A Dlockdep-design.rst150 could lead to the two contexts waiting for each other permanently. The
480 is not a deadlock for recursive read locks, as while the task B is waiting for
509 Task A is waiting for task B to read_unlock() Y and task B is waiting for task
634 waiting scenario and nobody can get progress, therefore a deadlock.
642 waiting scenario, means there are N CPU/tasks, where CPU/task P1 is waiting for
643 a lock held by P2, and P2 is waiting for a lock held by P3, ... and Pn is waiting
644 for a lock held by P1. Let's name the lock Px is waiting as Lx, so since P1 is waiting
654 the dependency Lx -> Lx+1, and since Px is waiting for Px+1 to release Lx,
/linux/arch/arm/mach-pxa/
H A Dsleep.S34 20: b 20b @ waiting for sleep
172 20: b 20b @ loop waiting for sleep
/linux/drivers/net/ethernet/cavium/liquidio/
H A Docteon_console.c426 console->waiting = 0; in octeon_console_handle_result()
501 if (console->waiting) in check_console()
617 if (console->waiting) in octeon_get_uboot_version()
668 console->waiting = 0; in octeon_add_console()
/linux/Documentation/devicetree/bindings/sound/
H A Drt5660.txt22 added delay time for waiting codec power ready.
/linux/Documentation/process/
H A Dvolatile-considered-harmful.rst37 want to play with that data will be waiting on the lock. The spinlock
62 when the processor is busy-waiting on the value of a variable. The right
71 waiting is generally an anti-social act to begin with.
/linux/drivers/firmware/arm_scmi/transports/
H A DKconfig62 in atomic context too, at the price of using a number of busy-waiting
120 in atomic context too, at the price of using a number of busy-waiting
/linux/drivers/gpu/drm/nouveau/nvkm/subdev/clk/
H A Dbase.c306 if (!atomic_xchg(&clk->waiting, 0)) in nvkm_pstate_work()
338 atomic_set(&clk->waiting, 1); in nvkm_pstate_calc()
341 wait_event(clk->wait, !atomic_read(&clk->waiting)); in nvkm_pstate_calc()
676 atomic_set(&clk->waiting, 0); in nvkm_clk_ctor()

1234567