| /kernel/linux/linux-5.10/net/smc/ |
| D | smc_tx.c | 89 conn->killed || in smc_tx_wait()
159 conn->killed) in smc_tx_sendmsg()
502 if (conn->killed) in smcr_tx_sndbuf_nonempty()
563 if (conn->killed || in smc_tx_sndbuf_nonempty()
625 if (conn->killed || in smc_tx_consumer_update()
629 !conn->killed) { in smc_tx_consumer_update()
|
| D | smc_rx.c | 209 conn->killed || in smc_rx_wait()
313 if (conn->killed) in smc_rx_recvmsg()
|
| D | smc_close.c | 69 smc->conn.killed, in smc_close_stream_wait()
98 if (conn->killed) in smc_close_final()
|
| D | smc.h | 213 u8 killed : 1; /* abnormal termination */ member
|
| D | smc_cdc.c | 71 if (conn->killed) { in smc_cdc_get_free_slot()
400 if (!conn || conn->killed) in smcd_cdc_rx_tsklet()
|
| D | smc_ism.c | 430 if (conn && !conn->killed) in smcd_handle_irq()
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/nouveau/nvkm/engine/fifo/ |
| D | changf100.h | 13 bool killed; member
|
| D | changk104.h | 15 bool killed; member
|
| D | gpfifogf100.c | 166 if (!list_empty(&chan->head) && !chan->killed) { in gf100_fifo_gpfifo_fini()
188 if (list_empty(&chan->head) && !chan->killed) { in gf100_fifo_gpfifo_init()
|
| D | gpfifogk104.c | 213 if (list_empty(&chan->head) && !chan->killed) { in gk104_fifo_gpfifo_init()
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/nouveau/ |
| D | nouveau_chan.h | 54 atomic_t killed; member
|
| D | nouveau_chan.c | 54 atomic_set(&chan->killed, 1); in nouveau_channel_killed()
63 if (likely(chan && chan->fence && !atomic_read(&chan->killed))) { in nouveau_channel_idle()
163 atomic_set(&chan->killed, 0); in nouveau_channel_prep()
|
| /kernel/linux/linux-5.10/tools/testing/selftests/rcutorture/bin/ |
| D | kvm-recheck.sh | 45 echo QEMU killed
|
| D | kvm-test-1-run.sh | 247 echo "PID $qemu_pid killed due to run STOP request" >> $resdir/Warnings 2>&1
|
| /kernel/linux/linux-5.10/drivers/block/paride/ |
| D | Transition-notes | 106 Corollary 1: ps_tq_active can be killed. Indeed, the only place where we
112 Corollary 2: ps_spinlock can be killed. Indeed, Lemma 1 and Lemma 2 show
118 can be killed. Indeed, we are not holding pd_lock and thus pd_busy is already
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | overcommit-accounting.rst | 27 killed while accessing pages but will receive errors on memory
|
| /kernel/linux/linux-5.10/Documentation/driver-api/firmware/ |
| D | firmware_cache.rst | 47 * Upon suspend any pending non-uevent firmware requests are killed to avoid
|
| /kernel/linux/linux-5.10/tools/testing/selftests/arm64/signal/ |
| D | README | 36 - Most of these tests are successfully passing if the process gets killed by
|
| /kernel/linux/linux-5.10/tools/testing/selftests/arm64/fp/ |
| D | README | 20 The test runs until killed by the user.
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/cgroup-v1/ |
| D | memcg_test.rst | 288 will be killed by the kernel.
291 in other groups shouldn't be killed.
|
| /kernel/linux/linux-5.10/drivers/nvdimm/ |
| D | bus.c | 562 bool killed; in nd_device_unregister() local
588 killed = kill_device(dev); in nd_device_unregister()
591 if (!killed) in nd_device_unregister()
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-5.10/Documentation/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 …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/usb/ |
| D | callbacks.rst | 105 killed by usbcore. Note that in this case disconnect will be called some
|