/linux/tools/tracing/rtla/src/ |
H A D | timerlat_u.c | 108 int killed = 0; in timerlat_u_send_kill() local 116 killed++; in timerlat_u_send_kill() 121 return killed; in timerlat_u_send_kill()
|
/linux/Documentation/security/ |
H A D | sak.rst | 50 actually want killed. This is because these applications are 54 You can identify processes which will be killed by SAK with the 65 So ``gpm`` will be killed by SAK. This is a bug in gpm. It should
|
/linux/net/smc/ |
H A D | smc_tx.c | 92 conn->killed || in smc_tx_wait() 216 conn->killed) in smc_tx_sendmsg() 567 if (conn->killed) in smcr_tx_sndbuf_nonempty() 639 if (conn->killed || in smc_tx_sndbuf_nonempty() 713 if (conn->killed || in smc_tx_consumer_update() 717 !conn->killed) { in smc_tx_consumer_update()
|
H A D | smc_close.c | 72 smc->conn.killed, in smc_close_stream_wait() 101 if (conn->killed) in smc_close_final()
|
H A D | smc_cdc.c | 84 if (conn->killed) { in smc_cdc_get_free_slot() 449 if (!conn || conn->killed) in smcd_cdc_rx_tsklet()
|
H A D | smc.h | 280 u8 killed : 1; /* abnormal termination */ member
|
H A D | smc_loopback.c | 248 if (!conn || conn->killed) in smc_lo_move_data()
|
/linux/drivers/gpu/drm/nouveau/ |
H A D | nouveau_chan.h | 57 atomic_t killed; member
|
H A D | nouveau_chan.c | 46 atomic_set(&chan->killed, 1); in nouveau_channel_kill() 57 NV_PRINTK(warn, cli, "channel %d killed!\n", chan->chid); in nouveau_channel_killed() 59 if (unlikely(!atomic_read(&chan->killed))) in nouveau_channel_killed() 68 if (likely(chan && chan->fence && !atomic_read(&chan->killed))) { in nouveau_channel_idle() 159 atomic_set(&chan->killed, 0); in nouveau_channel_prep()
|
H A D | nouveau_exec.c | 182 if (unlikely(!atomic_read(&chan->killed))) in nouveau_exec_job_timeout() 375 if (unlikely(atomic_read(&chan->killed))) in nouveau_exec_ioctl_exec()
|
H A D | nouveau_fence.h | 49 int notify_ref, dead, killed; member
|
H A D | nouveau_fence.c | 99 fctx->killed = 1; in nouveau_fence_context_kill() 243 if (unlikely(fctx->killed)) { in nouveau_fence_emit()
|
/linux/tools/testing/selftests/rcutorture/bin/ |
H A D | kvm-recheck.sh | 52 echo QEMU killed
|
/linux/Documentation/mm/ |
H A D | overcommit-accounting.rst | 24 killed while accessing pages but will receive errors on memory
|
H A D | hwpoison.rst | 22 running process can just be killed directly instead. This implies
|
/linux/Documentation/driver-api/firmware/ |
H A D | firmware_cache.rst | 47 * Upon suspend any pending non-uevent firmware requests are killed to avoid
|
/linux/tools/testing/selftests/arm64/signal/ |
H A D | README | 36 - Most of these tests are successfully passing if the process gets killed by
|
/linux/tools/testing/selftests/arm64/fp/ |
H A D | README | 20 The test runs until killed by the user.
|
/linux/Documentation/admin-guide/cgroup-v1/ |
H A D | memcg_test.rst | 277 will be killed by the kernel. 280 in other groups shouldn't be killed.
|
/linux/drivers/nvdimm/ |
H A D | bus.c | 557 bool killed; in nd_device_unregister() local 583 killed = kill_device(dev); in nd_device_unregister() 586 if (!killed) in nd_device_unregister()
|
/linux/Documentation/arch/sparc/oradax/ |
H A D | dax-hv-api.txt | 33 …operation may be cancelled or killed via the ccb_kill API function. It is recommended for guest so… 131 referenced by a CCB must be pinned in memory until the CCB either completes execution or is killed 985 … 0x3 Command ran and was killed (partial execution may 1002 0x7 Command was killed 1367 … the virtual machine. It could not be killed and no action was taken. 1376 … will reflect the killed status, with the subsequent implications that 1395 …If the pipeline target CCB is killed but the pipeline source CCB was skipped, the completion area … 1396 … target CCB may contain status (4,0) "Command was skipped" instead of (3,7) "Command was killed". 1398 …If the pipeline source CCB is killed, the pipeline target CCB's completion status may read (1,0) "… 1399 … This does not mean the target CCB was processed; since the source CCB was killed, there was no [all …]
|
/linux/drivers/vhost/ |
H A D | vhost.c | 276 if (!worker->attachment_cnt || worker->killed) in __vhost_worker_flush() 424 worker->killed = true; in vhost_worker_killed() 700 if (worker->killed) { in __vhost_vq_attach_worker() 725 if (old_worker->killed) { in __vhost_vq_attach_worker() 807 if (worker->attachment_cnt || worker->killed) { in vhost_free_worker()
|
/linux/Documentation/driver-api/usb/ |
H A D | callbacks.rst | 107 killed by usbcore. Note that in this case disconnect will be called some
|
/linux/kernel/ |
H A D | fork.c | 1600 int killed; in wait_for_vfork_done() local 1603 killed = wait_for_completion_state(vfork, state); in wait_for_vfork_done() 1606 if (killed) { in wait_for_vfork_done() 1613 return killed; in wait_for_vfork_done()
|
/linux/arch/arc/kernel/ |
H A D | entry-compact.S | 208 ; User process needs to be killed with SIGBUS, but first need to get
|