/linux-6.6.21/tools/tracing/rtla/src/ |
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-6.6.21/Documentation/security/ |
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-6.6.21/net/smc/ |
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() 741 if (conn->killed || in smc_tx_consumer_update() 745 !conn->killed) { in smc_tx_consumer_update()
|
D | smc_close.c | 72 smc->conn.killed, in smc_close_stream_wait() 101 if (conn->killed) in smc_close_final()
|
D | smc_cdc.c | 83 if (conn->killed) { in smc_cdc_get_free_slot() 417 if (!conn || conn->killed) in smcd_cdc_rx_tsklet()
|
D | smc_rx.c | 273 conn->killed || in smc_rx_wait() 384 if (conn->killed) in smc_rx_recvmsg()
|
D | smc.h | 239 u8 killed : 1; /* abnormal termination */ member
|
/linux-6.6.21/drivers/gpu/drm/nouveau/ |
D | nouveau_chan.h | 59 atomic_t killed; member
|
D | nouveau_fence.h | 49 int notify_ref, dead, killed; member
|
D | nouveau_chan.c | 46 atomic_set(&chan->killed, 1); in nouveau_channel_kill() 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() 161 atomic_set(&chan->killed, 0); in nouveau_channel_prep()
|
D | nouveau_exec.c | 208 if (unlikely(!atomic_read(&chan->killed))) in nouveau_exec_job_timeout() 401 if (unlikely(atomic_read(&chan->killed))) in nouveau_exec_ioctl_exec()
|
D | nouveau_fence.c | 99 fctx->killed = 1; in nouveau_fence_context_kill() 242 if (unlikely(fctx->killed)) { in nouveau_fence_emit()
|
/linux-6.6.21/tools/testing/selftests/rcutorture/bin/ |
D | kvm-recheck.sh | 52 echo QEMU killed
|
/linux-6.6.21/Documentation/mm/ |
D | overcommit-accounting.rst | 25 killed while accessing pages but will receive errors on memory
|
/linux-6.6.21/tools/testing/selftests/arm64/signal/ |
D | README | 36 - Most of these tests are successfully passing if the process gets killed by
|
/linux-6.6.21/Documentation/driver-api/firmware/ |
D | firmware_cache.rst | 47 * Upon suspend any pending non-uevent firmware requests are killed to avoid
|
/linux-6.6.21/tools/testing/selftests/arm64/fp/ |
D | README | 20 The test runs until killed by the user.
|
/linux-6.6.21/Documentation/admin-guide/cgroup-v1/ |
D | memcg_test.rst | 277 will be killed by the kernel. 280 in other groups shouldn't be killed.
|
/linux-6.6.21/drivers/nvdimm/ |
D | bus.c | 554 bool killed; in nd_device_unregister() local 580 killed = kill_device(dev); in nd_device_unregister() 583 if (!killed) in nd_device_unregister()
|
/linux-6.6.21/Documentation/arch/sparc/oradax/ |
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-6.6.21/Documentation/arch/x86/ |
D | buslock.rst | 115 In this case, the bus lock is not tolerated and the process is killed.
|
/linux-6.6.21/drivers/net/wireless/intersil/orinoco/ |
D | orinoco_usb.c | 270 int killed; member 329 ctx->killed = 1; in ezusb_request_timerfn() 518 if (ctx->killed) { in ezusb_request_out_callback()
|
/linux-6.6.21/Documentation/driver-api/usb/ |
D | callbacks.rst | 105 killed by usbcore. Note that in this case disconnect will be called some
|
/linux-6.6.21/fs/ |
D | exec.c | 1076 goto killed; in de_thread() 1104 goto killed; in de_thread() 1171 killed: in de_thread()
|
/linux-6.6.21/arch/arc/kernel/ |
D | entry-compact.S | 208 ; User process needs to be killed with SIGBUS, but first need to get
|