| /linux-4.4.14/Documentation/ |
| D | SAK.txt | 47 actually want killed. This is because these applications are
51 You can identify processes which will be killed by SAK with the
62 So `gpm' will be killed by SAK. This is a bug in gpm. It should
|
| D | atomic_ops.txt | 474 obj->killed = 1;
480 "obj->killed = 1;" is visible.
|
| D | sysrq.txt | 79 panic if nothing can be killed.
|
| /linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/engine/fifo/ |
| D | changf100.h | 12 bool killed; member
|
| D | changk104.h | 13 bool killed; member
|
| D | gpfifogf100.c | 140 if (!list_empty(&chan->head) && !chan->killed) { in gf100_fifo_gpfifo_fini()
162 if (list_empty(&chan->head) && !chan->killed) { in gf100_fifo_gpfifo_init()
|
| D | gpfifogk104.c | 174 if (list_empty(&chan->head) && !chan->killed) { in gk104_fifo_gpfifo_init()
|
| D | gf100.c | 161 chan->killed = true; in gf100_fifo_recover()
|
| D | gk104.c | 136 chan->killed = true; in gk104_fifo_recover()
|
| /linux-4.4.14/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-4.4.14/drivers/staging/android/ |
| D | Kconfig | 34 Registers processes to be killed when low memory conditions, this is useful
|
| /linux-4.4.14/Documentation/vm/ |
| D | overcommit-accounting | 19 this means a process will not be killed while accessing
|
| D | hwpoison.txt | 17 * running process can just be killed directly instead. This implies
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | memcg_test.txt | 229 will be killed by the kernel.
231 in other groups shouldn't be killed.
|
| /linux-4.4.14/arch/blackfin/ |
| D | Kconfig.debug | 45 signal to be killed. If you are getting HW errors in your system,
97 Misbehaving applications will be killed (generate a SEGV) while the
|
| /linux-4.4.14/kernel/ |
| D | fork.c | 828 int killed; in wait_for_vfork_done() local
831 killed = wait_for_completion_killable(vfork); in wait_for_vfork_done()
834 if (killed) { in wait_for_vfork_done()
841 return killed; in wait_for_vfork_done()
|
| /linux-4.4.14/drivers/net/wireless/orinoco/ |
| D | orinoco_usb.c | 273 int killed; member
332 ctx->killed = 1; in ezusb_request_timerfn()
533 if (ctx->killed) { in ezusb_request_out_callback()
|
| /linux-4.4.14/fs/ |
| D | exec.c | 925 goto killed; in de_thread()
953 goto killed; in de_thread()
1049 killed: in de_thread()
|
| /linux-4.4.14/Documentation/usb/ |
| D | callbacks.txt | 86 killed by usbcore. Note that in this case disconnect will be called some
|
| D | usbmon.txt | 75 This process will read until it is killed. Naturally, the output can be
|
| /linux-4.4.14/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-4.4.14/arch/arc/kernel/ |
| D | entry-compact.S | 225 ; User process needs to be killed with SIGBUS, but first need to get
|
| /linux-4.4.14/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-4.4.14/arch/cris/arch-v10/kernel/ |
| D | entry.S | 408 ;; do the RBFexit since we might have killed off the running
|
| /linux-4.4.14/Documentation/target/ |
| D | tcmu-design.txt | 234 Userspace handler process is killed:
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | vm.txt | 597 memory when killed.
687 may be killed by oom-killer. No panic occurs in this case.
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | cxlflash.txt | 158 such as a killed process. This design point is described in further
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | proc.txt | 1441 process gets killed in out of memory conditions.
1490 avoids servers and important system daemons from being killed and loses the
1499 process should be killed in an out-of-memory situation.
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | CHANGES | 401 cifs stats. Fix oops in unmount when cifsd thread being killed by
576 to kernel log when application with open network files killed.
|
| /linux-4.4.14/drivers/watchdog/ |
| D | Kconfig | 46 get killed. If you say Y here, the watchdog cannot be stopped once
|
| /linux-4.4.14/drivers/scsi/aic7xxx/ |
| D | aic7xxx.seq | 1446 * instead of being killed by SCSIEN getting cleared.
|
| /linux-4.4.14/Documentation/trace/ |
| D | ftrace.txt | 167 if it were to be killed by a signal, this file can be used
|
| /linux-4.4.14/drivers/staging/speakup/ |
| D | spkguide.txt | 986 be categorized. You will find messages such as "You killed Speakup",
|
| /linux-4.4.14/Documentation/scsi/ |
| D | ChangeLog.lpfc | 1387 modprobe are killed via ctrl-c
|