| /Linux-v5.4/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-v5.4/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 | 189 chan->killed = true; in gf100_fifo_recover()
|
| /Linux-v5.4/drivers/gpu/drm/nouveau/ |
| D | nouveau_chan.h | 48 atomic_t killed; member
|
| D | nouveau_chan.c | 57 atomic_set(&chan->killed, 1); in nouveau_channel_killed()
64 if (likely(chan && chan->fence && !atomic_read(&chan->killed))) { in nouveau_channel_idle()
139 atomic_set(&chan->killed, 0); in nouveau_channel_prep()
|
| /Linux-v5.4/tools/testing/selftests/rcutorture/bin/ |
| D | kvm-recheck.sh | 41 echo QEMU killed
|
| /Linux-v5.4/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-v5.4/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-v5.4/Documentation/driver-api/firmware/ |
| D | firmware_cache.rst | 47 * Upon suspend any pending non-uevent firmware requests are killed to avoid
|
| /Linux-v5.4/Documentation/admin-guide/cgroup-v1/ |
| D | memcg_test.rst | 288 will be killed by the kernel.
291 in other groups shouldn't be killed.
|
| /Linux-v5.4/drivers/nvdimm/ |
| 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-v5.4/drivers/net/wireless/intersil/orinoco/ |
| D | orinoco_usb.c | 270 int killed; member
329 ctx->killed = 1; in ezusb_request_timerfn()
529 if (ctx->killed) { in ezusb_request_out_callback()
|
| /Linux-v5.4/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-v5.4/fs/ |
| D | exec.c | 1093 goto killed; in de_thread()
1121 goto killed; in de_thread()
1220 killed: in de_thread()
|
| /Linux-v5.4/Documentation/driver-api/usb/ |
| D | callbacks.rst | 105 killed by usbcore. Note that in this case disconnect will be called some
|
| /Linux-v5.4/kernel/ |
| D | fork.c | 1255 int killed; in wait_for_vfork_done() local
1259 killed = wait_for_completion_killable(vfork); in wait_for_vfork_done()
1263 if (killed) { in wait_for_vfork_done()
1270 return killed; in wait_for_vfork_done()
|
| /Linux-v5.4/arch/arc/kernel/ |
| D | entry-compact.S | 208 ; User process needs to be killed with SIGBUS, but first need to get
|
| /Linux-v5.4/Documentation/security/keys/ |
| D | request-key.rst | 52 killed off as a group.
|
| /Linux-v5.4/Documentation/core-api/ |
| D | atomic_ops.rst | 495 obj->killed = 1;
501 "obj->killed = 1;" is visible.
|
| /Linux-v5.4/Documentation/admin-guide/mm/ |
| D | concepts.rst | 222 system health. The selected task is killed in a hope that after it exits
|
| /Linux-v5.4/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
|
