| /Linux-v4.19/Documentation/ |
| D | SAK.txt | 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-v4.19/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()
|
| D | gf100.c | 188 chan->killed = true; in gf100_fifo_recover()
|
| /Linux-v4.19/drivers/gpu/drm/nouveau/ |
| D | nouveau_chan.h | 45 atomic_t killed; member
|
| D | nouveau_chan.c | 55 atomic_set(&chan->killed, 1); in nouveau_channel_killed()
62 if (likely(chan && chan->fence && !atomic_read(&chan->killed))) { in nouveau_channel_idle()
132 atomic_set(&chan->killed, 0); in nouveau_channel_prep()
|
| /Linux-v4.19/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
|
| /Linux-v4.19/Documentation/vm/ |
| D | overcommit-accounting.rst | 27 killed while accessing pages but will receive errors on memory
|
| D | hwpoison.rst | 24 * running process can just be killed directly instead. This implies
|
| /Linux-v4.19/Documentation/driver-api/firmware/ |
| D | firmware_cache.rst | 47 * Upon suspend any pending non-uevent firmware requests are killed to avoid
|
| /Linux-v4.19/Documentation/cgroup-v1/ |
| D | memcg_test.txt | 229 will be killed by the kernel.
231 in other groups shouldn't be killed.
|
| /Linux-v4.19/drivers/net/wireless/intersil/orinoco/ |
| D | orinoco_usb.c | 274 int killed; member
333 ctx->killed = 1; in ezusb_request_timerfn()
533 if (ctx->killed) { in ezusb_request_out_callback()
|
| /Linux-v4.19/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 …]
|
| /Linux-v4.19/kernel/ |
| D | fork.c | 1177 int killed; in wait_for_vfork_done() local
1180 killed = wait_for_completion_killable(vfork); in wait_for_vfork_done()
1183 if (killed) { in wait_for_vfork_done()
1190 return killed; in wait_for_vfork_done()
|
| /Linux-v4.19/fs/ |
| D | exec.c | 1088 goto killed; in de_thread()
1116 goto killed; in de_thread()
1215 killed: in de_thread()
|
| /Linux-v4.19/Documentation/driver-api/usb/ |
| D | callbacks.rst | 105 killed by usbcore. Note that in this case disconnect will be called some
|
| /Linux-v4.19/Documentation/blockdev/ |
| D | README.DAC960 | 373 have been killed simultaneously, this command may be used to bring all but
458 DAC960#0: Physical Drive 1:1 killed because of timeout on SCSI command
492 functioning drive, or if the physical drive was killed without having failed
629 DAC960#0: Physical Drive 1:2 killed because of timeout on SCSI command
631 DAC960#0: Physical Drive 1:2 killed because it was removed
|
| /Linux-v4.19/arch/arc/kernel/ |
| D | entry-compact.S | 211 ; User process needs to be killed with SIGBUS, but first need to get
|
| /Linux-v4.19/Documentation/core-api/ |
| D | atomic_ops.rst | 495 obj->killed = 1;
501 "obj->killed = 1;" is visible.
|
| /Linux-v4.19/Documentation/admin-guide/mm/ |
| D | concepts.rst | 221 selected task is killed in a hope that after it exits enough memory
|
| /Linux-v4.19/Documentation/filesystems/caching/ |
| D | backend-api.txt | 688 (*) Indicate that the caching backend killed an object:
693 This is called to indicate that the cache backend preemptively killed an
|
| /Linux-v4.19/Documentation/admin-guide/ |
| D | sysrq.rst | 97 panic if nothing can be killed.
|
| /Linux-v4.19/Documentation/locking/ |
| D | ww-mutex-design.txt | 78 killed its transaction after having dropped all already acquired locks.
|
