Home
last modified time | relevance | path

Searched refs:kill (Results 1 – 143 of 143) sorted by relevance

/linux-4.4.14/tools/perf/tests/attr/
DREADME35 perf record kill (test-record-basic)
36 perf record -b kill (test-record-branch-any)
37 perf record -j any kill (test-record-branch-filter-any)
38 perf record -j any_call kill (test-record-branch-filter-any_call)
39 perf record -j any_ret kill (test-record-branch-filter-any_ret)
40 perf record -j hv kill (test-record-branch-filter-hv)
41 perf record -j ind_call kill (test-record-branch-filter-ind_call)
42 perf record -j k kill (test-record-branch-filter-k)
43 perf record -j u kill (test-record-branch-filter-u)
44 perf record -c 123 kill (test-record-count)
[all …]
Dtest-record-basic3 args = kill >/dev/null 2>&1
Dtest-record-freq3 args = -F 100 kill >/dev/null 2>&1
Dtest-record-no-samples3 args = -n kill >/dev/null 2>&1
Dtest-record-graph-default3 args = -g kill >/dev/null 2>&1
Dtest-record-no-inherit3 args = -i kill >/dev/null 2>&1
Dtest-stat-basic3 args = -e cycles kill >/dev/null 2>&1
Dtest-record-raw3 args = -R kill >/dev/null 2>&1
Dtest-record-branch-any3 args = -b kill >/dev/null 2>&1
Dtest-record-graph-fp3 args = --call-graph fp kill >/dev/null 2>&1
Dtest-record-count3 args = -c 123 kill >/dev/null 2>&1
Dtest-record-period3 args = -c 100 -P kill >/dev/null 2>&1
Dtest-record-branch-filter-hv3 args = -j hv kill >/dev/null 2>&1
Dtest-record-branch-filter-u3 args = -j u kill >/dev/null 2>&1
Dtest-record-branch-filter-k3 args = -j k kill >/dev/null 2>&1
Dtest-record-branch-filter-ind_call3 args = -j ind_call kill >/dev/null 2>&1
Dtest-record-branch-filter-any3 args = -j any kill >/dev/null 2>&1
Dtest-record-branch-filter-any_ret3 args = -j any_ret kill >/dev/null 2>&1
Dtest-stat-no-inherit3 args = -i -e cycles kill >/dev/null 2>&1
Dtest-record-branch-filter-any_call3 args = -j any_call kill >/dev/null 2>&1
Dtest-record-no-delay3 args = -D kill >/dev/null 2>&1
Dtest-record-data3 args = -d kill >/dev/null 2>&1
Dtest-stat-group13 args = -e '{cycles,instructions}' kill >/dev/null 2>&1
Dtest-stat-group3 args = --group -e cycles,instructions kill >/dev/null 2>&1
Dtest-stat-C03 args = -e cycles -C 0 kill >/dev/null 2>&1
Dtest-record-graph-dwarf3 args = --call-graph dwarf -- kill >/dev/null 2>&1
Dtest-record-C03 args = -C 0 kill >/dev/null 2>&1
Dtest-record-group3 args = --group -e cycles,instructions kill >/dev/null 2>&1
Dtest-record-group13 args = -e '{cycles,instructions}' kill >/dev/null 2>&1
Dtest-record-group-sampling3 args = -e '{cycles,cache-misses}:S' kill >/dev/null 2>&1
Dtest-stat-default3 args = kill >/dev/null 2>&1
Dtest-stat-detailed-13 args = -d kill >/dev/null 2>&1
Dtest-stat-detailed-23 args = -dd kill >/dev/null 2>&1
Dtest-stat-detailed-33 args = -ddd kill >/dev/null 2>&1
/linux-4.4.14/include/linux/
Dfs_pin.h8 void (*kill)(struct fs_pin *); member
13 static inline void init_fs_pin(struct fs_pin *p, void (*kill)(struct fs_pin *)) in init_fs_pin()
18 p->kill = kill; in init_fs_pin()
/linux-4.4.14/Documentation/devicetree/bindings/power/reset/
Dltc2952-poweroff.txt5 A full powerdown can be triggered via the kill signal.
12 - kill-gpios: phandle + gpio-specifier for the GPIO connected to the
13 chip's kill line
19 until an explicit kill signal is received
28 kill-gpios = <&gpio0 2 GPIO_ACTIVE_LOW>;
/linux-4.4.14/fs/
Dfs_struct.c98 int kill; in exit_fs() local
102 kill = !--fs->users; in exit_fs()
105 if (kill) in exit_fs()
135 int kill; in unshare_fs_struct() local
142 kill = !--fs->users; in unshare_fs_struct()
147 if (kill) in unshare_fs_struct()
Dinode.c1674 int kill = 0; in should_remove_suid() local
1678 kill = ATTR_KILL_SUID; in should_remove_suid()
1685 kill |= ATTR_KILL_SGID; in should_remove_suid()
1687 if (unlikely(kill && !capable(CAP_FSETID) && S_ISREG(mode))) in should_remove_suid()
1688 return kill; in should_remove_suid()
1718 static int __remove_privs(struct dentry *dentry, int kill) in __remove_privs() argument
1722 newattrs.ia_valid = ATTR_FORCE | kill; in __remove_privs()
1738 int kill; in file_remove_privs() local
1745 kill = file_needs_remove_privs(file); in file_remove_privs()
1746 if (kill < 0) in file_remove_privs()
[all …]
Dfs_pin.c49 p->kill(p); in pin_kill()
Dpipe.c538 int kill = 0; in put_pipe_info() local
543 kill = 1; in put_pipe_info()
547 if (kill) in put_pipe_info()
/linux-4.4.14/arch/um/os-Linux/
Dutil.c93 if (kill(getpid(), SIGABRT) < 0) in uml_abort()
121 kill(0, SIGTERM); in os_dump_core()
127 kill(0, SIGCONT); in os_dump_core()
Dprocess.c95 kill(pid, SIGALRM); in os_alarm_process()
100 kill(pid, SIGSTOP); in os_stop_process()
105 kill(pid, SIGKILL); in os_kill_process()
117 kill(pid, SIGKILL); in os_kill_ptraced_process()
Dstart_up.c38 kill(pid, SIGKILL); in ptrace_child()
40 kill(pid, SIGSTOP); in ptrace_child()
Dumid.c176 if ((kill(p, 0) == 0) || (errno != ESRCH)) { in is_umdir_used()
/linux-4.4.14/tools/testing/selftests/powerpc/
Dharness.c60 kill(-pid, SIGKILL); in run_test()
64 kill(-pid, SIGTERM); in run_test()
72 kill(-pid, SIGTERM); in run_test()
/linux-4.4.14/arch/frv/mm/
Dtlb-flush.S50 # kill cached PGE value
55 # kill AMPR-cached TLB values
94 # kill cached PGE value
134 # kill cached PGE value
162 # kill cached PGE value
/linux-4.4.14/Documentation/vm/
Dhwpoison.txt5 kill the processes associated with it and avoid using it in the future.
58 early kill
65 late kill
68 Note some pages are always handled as late kill.
78 Enable early kill mode globally
81 Set early/late kill mode/revert to system default
84 PR_MCE_KILL_EARLY: Early kill
85 PR_MCE_KILL_LATE: Late kill
Dunevictable-lru.txt144 the control group to thrash or to OOM-kill tasks.
/linux-4.4.14/arch/mn10300/mm/
Dcache-inv-by-tag.S194 mov d2,(L1_CACHE_WAYDISP*0,a0) # kill the tag
208 mov d2,(L1_CACHE_WAYDISP*1,a0) # kill the tag
222 mov d2,(L1_CACHE_WAYDISP*2,a0) # kill the tag
236 mov d2,(L1_CACHE_WAYDISP*3,a0) # kill the tag
/linux-4.4.14/tools/testing/selftests/breakpoints/
Dbreakpoint_test.c139 kill(getpid(), SIGUSR1); in check_trapped()
214 kill(getpid(), SIGUSR1); in trigger_tests()
259 kill(getpid(), SIGUSR1); in trigger_tests()
/linux-4.4.14/Documentation/networking/
DREADME.ipw2100163 0 = RF kill not enabled (radio on)
164 1 = SW based RF kill active (radio off)
165 2 = HW based RF kill active (radio off)
166 3 = Both HW and SW RF kill active (radio off)
168 0 = If SW based RF kill active, turn the radio back on
169 1 = If radio is on, activate SW based RF kill
171 NOTE: If you enable the SW based RF kill and then toggle the HW
172 based RF kill from ON -> OFF -> ON, the radio will NOT come back on
182 RF kill switch"
DREADME.ipw2200293 0 = RF kill not enabled (radio on)
294 1 = SW based RF kill active (radio off)
295 2 = HW based RF kill active (radio off)
296 3 = Both HW and SW RF kill active (radio off)
298 0 = If SW based RF kill active, turn the radio back on
299 1 = If radio is on, activate SW based RF kill
301 NOTE: If you enable the SW based RF kill and then toggle the HW
302 based RF kill from ON -> OFF -> ON, the radio will NOT come back on
Darcnet.txt512 D_DURING or more, it would be a REALLY good idea to kill your klogd daemon
Dip-sysctl.txt334 tcp_keepalive_probes it is time to kill not responding connection,
354 and tune network services to linger and kill such states
Drxrpc.txt909 before we preemptively kill it.
/linux-4.4.14/security/apparmor/
Dfile.c139 if (sa.aad->fs.request & perms->kill) in aa_audit_file()
204 perms.kill = 0; in compute_perms()
395 lperms.kill = perms.kill; in aa_path_link()
Dcapability.c84 cap_raised(profile->caps.kill, cap)) { in audit_caps()
Ddomain.c106 perms.audit = perms.quiet = perms.kill = 0; in change_profile_perms()
698 perms.kill = AA_MAY_CHANGEHAT; in aa_change_hat()
709 perms.kill = AA_MAY_CHANGEHAT; in aa_change_hat()
/linux-4.4.14/security/apparmor/include/
Dcapability.h35 kernel_cap_t kill; member
Dfile.h91 u32 kill; member
97 #define COMBINED_PERM_MASK(X) ((X).allow | (X).audit | (X).quiet | (X).kill)
/linux-4.4.14/tools/testing/selftests/powerpc/pmu/
Dlib.c118 kill(child_pid, SIGTERM); in kill_child_and_wait()
171 kill(pid, SIGKILL); in eat_cpu()
/linux-4.4.14/samples/bpf/
Dtrace_output_user.c141 kill(0, SIGINT); in print_bpf_output()
149 kill(0, SIGINT); in print_bpf_output()
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-memory-page-offline18 kernel will never kill anything for this, but rather
33 triggering IO errors if needed. Note this may kill
Dsysfs-firmware-acpi176 Let's take power button fixed event for example, please kill acpid
/linux-4.4.14/arch/um/kernel/
Dtlb.c407 goto kill; in flush_tlb_page()
411 goto kill; in flush_tlb_page()
415 goto kill; in flush_tlb_page()
450 goto kill; in flush_tlb_page()
457 kill: in flush_tlb_page()
/linux-4.4.14/drivers/tty/vt/
Dvc_screen.c96 struct vcs_poll_data *poll = file->private_data, *kill = NULL; in vcs_poll_data_get() local
125 kill = poll; in vcs_poll_data_get()
129 if (kill) in vcs_poll_data_get()
130 vcs_poll_data_free(kill); in vcs_poll_data_get()
/linux-4.4.14/tools/testing/selftests/seccomp/
Dseccomp_bpf.c741 struct sock_fprog kill; in FIXTURE_DATA() local
788 FILTER_ALLOC(kill); in FIXTURE_SETUP()
798 FILTER_FREE(kill); in FIXTURE_TEARDOWN()
818 ret = prctl(PR_SET_SECCOMP, SECCOMP_MODE_FILTER, &self->kill); in TEST_F()
842 ret = prctl(PR_SET_SECCOMP, SECCOMP_MODE_FILTER, &self->kill); in TEST_F_SIGNAL()
863 ret = prctl(PR_SET_SECCOMP, SECCOMP_MODE_FILTER, &self->kill); in TEST_F_SIGNAL()
1040 kill(tracee, SIGKILL); in tracer()
1048 kill(tracee, SIGKILL); in tracer()
1117 ASSERT_EQ(0, kill(tracer, SIGUSR1)); in teardown_trace_fixture()
1140 kill(tracee, SIGKILL); in tracer_poke()
[all …]
/linux-4.4.14/drivers/input/keyboard/
Dlm8323.c440 static void lm8323_write_pwm(struct lm8323_pwm *pwm, int kill, in lm8323_write_pwm() argument
448 lm8323_write_pwm_one(pwm, i++, PWM_END(kill)); in lm8323_write_pwm()
456 int div512, perstep, steps, hz, up, kill; in lm8323_pwm_work() local
471 kill = (pwm->desired_brightness == 0); in lm8323_pwm_work()
502 lm8323_write_pwm(pwm, kill, num_cmds, pwm_cmds); in lm8323_pwm_work()
/linux-4.4.14/drivers/staging/vt6656/
DTODO10 - kill ttype.h -- done
/linux-4.4.14/drivers/staging/vt6655/
DTODO10 - kill ttype.h
/linux-4.4.14/tools/testing/selftests/powerpc/pmu/ebb/
Dmulti_ebb_procs_test.c100 kill(pids[i], SIGINT); in multi_ebb_procs()
/linux-4.4.14/tools/perf/arch/x86/tests/
Dintel-cqm.c119 kill(pid, SIGKILL); in test__intel_cqm_count_nmi_context()
/linux-4.4.14/Documentation/
Dsysrq.txt26 64 = 0x40 - enable signalling of processes (term, kill, oom-kill)
78 'f' - Will call the oom killer to kill a memory hog process, but do not
140 when you would try to login. It will kill all programs on given console,
172 term(e) and kill(i) are useful if you have some sort of runaway process you
173 are unable to kill any other way, especially if it's spawning other
DSAK.txt20 once defined, SAK will kill a running X server. If the system is in
Drobust-futexes.txt29 pthread_mutex_t, or yum is kill -9-ed), then waiters for that lock need
46 In practice, when e.g. yum is kill -9-ed (or segfaults), a system reboot
Drfkill.txt1 rfkill - RF kill switch support
D00-INDEX389 - info on the radio frequency kill switch subsystem/support.
Dkernel-parameters.txt2653 oops=panic Always panic on oopses. Default is to just kill the
/linux-4.4.14/Documentation/ABI/obsolete/
Dsysfs-class-rfkill1 rfkill - radio frequency (RF) connector kill switch support
/linux-4.4.14/arch/um/drivers/
Dslirp_user.c94 if (kill(pri->pid, SIGHUP)<0) { in slirp_close()
/linux-4.4.14/lib/
Dklist.c210 static void klist_put(struct klist_node *n, bool kill) in klist_put() argument
216 if (kill) in klist_put()
/linux-4.4.14/Documentation/DocBook/
Dusb.xml.db41 API-usb-kill-urb
44 API-usb-kill-anchored-urbs
Dnetworking.xml.db158 API-skb-kill-datagram
184 API-gen-kill-estimator
Ddevice-drivers.xml.db167 API-sys-kill
/linux-4.4.14/Documentation/sysctl/
Dvm.txt72 That should provide enough for the admin to log in and kill a process,
81 sshd or login + bash (or some other shell) + top (or ps, kill, etc.)
388 Control how to kill processes when uncorrected memory error (typically
393 no other uptodate copy of the data it will kill to prevent any data
401 0: Only unmap the corrupted page from all processes and only kill a process
404 The kill is done using a catchable SIGBUS with BUS_MCEERR_AO, so processes can
574 the OOM killer chose the task it did to kill.
595 tasklist and select a task based on heuristics to kill. This normally
680 If this is set to 0, the kernel will kill some rogue process,
681 called oom_killer. Usually, oom_killer can kill rogue processes and
[all …]
/linux-4.4.14/arch/m68k/fpsp040/
Dbugfix.S254 | exceptional, we choose to kill the process.
342 | fpsp_fmt_error and allow the kernel to kill the process.
376 | exceptional, we choose to kill the process.
482 | to the entry point used to kill a process.
/linux-4.4.14/arch/mips/kernel/
Dvpe-cmp.c38 static DEVICE_ATTR(kill, S_IWUSR, NULL, store_kill);
Dvpe-mt.c277 static DEVICE_ATTR(kill, S_IWUSR, NULL, store_kill);
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-class-rfkill1 rfkill - radio frequency (RF) connector kill switch support
/linux-4.4.14/arch/alpha/lib/
Dstxcpy.S224 zapnot t1, t6, t1 # .. e1 : kill source bytes >= null
225 zap t0, t8, t0 # e0 : kill dest bytes <= null
Dev6-stxcpy.S250 zapnot t1, t6, t1 # U : kill source bytes >= null (stall)
252 zap t0, t8, t0 # U : kill dest bytes <= null (2 cycle data stall)
Dstxncpy.S260 zapnot t0, t8, t0 # .. e1 : kill source bytes > null
261 zap t1, t8, t1 # e0 : kill dest bytes <= null
Dev6-stxncpy.S303 zapnot t0, t8, t0 # U : kill source bytes > null
305 zap t1, t8, t1 # U : kill dest bytes <= null
/linux-4.4.14/Documentation/cgroups/
Dfreezer-subsystem.txt35 $ kill -SIGSTOP 16690
36 $ kill -SIGCONT 16690
Dmemcg_test.txt222 # kill malloc task.
227 Out-of-memory caused by memcg's limit will kill tasks under
Dmemory.txt247 an OOM routine is invoked to select and kill the bulkiest task in the
764 * kill some tasks.
/linux-4.4.14/Documentation/x86/
Dearlyprintk.txt126 …loglevel(0-9) reBoot Crashdump terminate-all-tasks(E) memory-full-oom-kill(F) kill-all-tasks(I) sa…
/linux-4.4.14/Documentation/usb/
Danchors.txt31 is automatic. A function is provided to forcibly finish (kill)
/linux-4.4.14/arch/s390/kernel/
Dreipl.S113 srl %r14,1 # need to kill hi bit to avoid specification exceptions.
/linux-4.4.14/fs/nfs/
Dwrite.c1380 int kill = 0; in nfs_should_remove_suid() local
1384 kill = ATTR_KILL_SUID; in nfs_should_remove_suid()
1391 kill |= ATTR_KILL_SGID; in nfs_should_remove_suid()
1393 if (unlikely(kill && S_ISREG(mode))) in nfs_should_remove_suid()
1394 return kill; in nfs_should_remove_suid()
/linux-4.4.14/net/ipv4/
Dtcp_minisocks.c131 goto kill; in tcp_timewait_state_process()
199 kill: in tcp_timewait_state_process()
/linux-4.4.14/mm/
Dmemory-failure.c951 int kill = 1, forcekill; in hwpoison_user_mappings() local
993 kill = 0; in hwpoison_user_mappings()
1009 if (kill) in hwpoison_user_mappings()
/linux-4.4.14/Documentation/scsi/
Ddc395x.txt100 reliable driver, there is a chance, that it will kill your valuable data.
DChangeLog.sym53c8xx_2124 - Use del_timer_sync() for recent kernels to kill the driver timer
DChangeLog.megaraid_sas225 f). Before driver kill adapter, driver will do last chance of
233 failed state. Driver will kill adapter if can't bring back FW after the
DChangeLog.megaraid241 overcautious programming will kill your kernel ;)
254 will kill your kernel ...
DChangeLog.lpfc62 - kill struct lpfc_scsi_dma_buf and embedded the two members
1386 * Free irq reservation and kill running timers when insmod or
/linux-4.4.14/tools/perf/
Dbuiltin-stat.c329 kill(child_pid, SIGTERM); in __run_perf_stat()
915 kill(child_pid, SIGTERM); in sig_atexit()
923 kill(getpid(), signr); in sig_atexit()
Dbuiltin-record.c735 kill(rec->evlist->workload.pid, SIGTERM); in __cmd_record()
/linux-4.4.14/Documentation/x86/x86_64/
Dmachinecheck52 risky for the kernel to kill a process because it defies
/linux-4.4.14/ipc/
Dmsg.c175 static void ss_wakeup(struct list_head *h, int kill) in ss_wakeup() argument
180 if (kill) in ss_wakeup()
/linux-4.4.14/arch/parisc/kernel/
Dsyscall_table.S105 ENTRY_SAME(kill)
/linux-4.4.14/arch/um/os-Linux/skas/
Dprocess.c239 kill(os_getpid(), SIGSTOP); in userspace_tramp()
/linux-4.4.14/arch/powerpc/include/asm/
Dsystbl.h43 SYSCALL_SPU(kill)
/linux-4.4.14/fs/ocfs2/dlm/
Ddlmmaster.c1887 goto kill; in dlm_assert_master_handler()
1912 goto kill; in dlm_assert_master_handler()
1920 goto kill; in dlm_assert_master_handler()
1930 goto kill; in dlm_assert_master_handler()
2057 kill: in dlm_assert_master_handler()
/linux-4.4.14/tools/testing/selftests/memfd/
Dmemfd_test.c532 kill(pid, SIGTERM); in join_idle_thread()
/linux-4.4.14/arch/x86/entry/syscalls/
Dsyscall_64.tbl71 62 common kill sys_kill
Dsyscall_32.tbl46 37 i386 kill sys_kill
/linux-4.4.14/fs/jffs2/
DREADME.Locking94 pointer when the garbage collection thread exits. The code to kill the
/linux-4.4.14/Documentation/trace/
Dmmiotrace.txt71 The 'cat' process exits. If it does not, kill it by issuing 'fg' command and
/linux-4.4.14/tools/lguest/
Dlguest.c1002 kill(0, SIGINT); in console_input()
1143 kill(0, SIGTERM); in kill_launcher()
1178 kill(vq->thread, SIGTERM); in reset_device()
/linux-4.4.14/drivers/staging/lustre/lustre/lov/
Dlov_obd.c85 LIST_HEAD(kill); in lov_putref()
96 list_add(&tgt->ltd_kill, &kill); in lov_putref()
106 list_for_each_entry_safe(tgt, n, &kill, ltd_kill) { in lov_putref()
/linux-4.4.14/Documentation/isdn/
DsyncPPP.FAQ128 I found to do this is to kill the ipppd and
DREADME.gigaset78 discipline remains active. To deactivate it, kill the daemon, for example
DREADME354 any of the modules, kill iprofd first.
/linux-4.4.14/fs/affs/
DChanges33 - kill kernel lock
/linux-4.4.14/drivers/nvme/host/
Dpci.c2541 bool kill = nvme_io_incapable(ns->dev) && !blk_queue_dying(ns->queue); in nvme_ns_remove() local
2543 if (kill) { in nvme_ns_remove()
2556 if (kill || !blk_queue_dying(ns->queue)) { in nvme_ns_remove()
/linux-4.4.14/Documentation/blockdev/
DREADME.DAC960363 kill <channel>:<target-id>
365 The "kill" command marks the physical drive <channel>:<target-id> as DEAD.
/linux-4.4.14/Documentation/filesystems/
Dproc.txt1444 (never kill) to 1000 (always kill) to determine which process is targeted. The
1463 is used to determine which task to kill. Acceptable values range from -1000
1878 pid value exists (it can be learned by other means, e.g. by "kill -0 $PID"),
Dramfs-rootfs-initramfs.txt75 same reason you can't kill the init process; rather than having special code
DLocking485 ->ioctl() or kill the latter completely. One of the problems is that for
/linux-4.4.14/Documentation/mic/mpssd/
Dmpssd.c1505 ret = kill(mic->pid, SIGTERM); in mic_config()
/linux-4.4.14/Documentation/video4linux/
DZoran394 I woke up, and can't go to sleep again. I'll kill some time explaining why
/linux-4.4.14/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt2839 host% kill -USR1 20093
3184 30 kill(pid, SIGUSR1);
3471 kill -USR1 4127
4183 host% kill -STOP pid
4216 kill -CONT pid
/linux-4.4.14/Documentation/filesystems/cifs/
DCHANGES362 recommended, unmount and rmmod cifs will kill them when they are
508 Do not kill cifsd (and thus hurt the other SMB session) when more than one
/linux-4.4.14/drivers/platform/x86/
DKconfig826 tristate "OLPC XO-1 software RF kill switch"
/linux-4.4.14/tools/perf/Documentation/
Dintel-pt.txt445 kill -USR2 11435
/linux-4.4.14/kernel/
Dsignal.c2847 SYSCALL_DEFINE2(kill, pid_t, pid, int, sig) in SYSCALL_DEFINE2() argument
/linux-4.4.14/Documentation/security/
DSmack.txt504 attempts. Sending a signal via the kill() system call is a write operation
/linux-4.4.14/Documentation/s390/
DDebugging390.txt1320 completed successfully) and HALT SUBCHANNEL (to kill IO). A subchannel can have
1850 kill -SIGSEGV <gdb's pid>
/linux-4.4.14/arch/arm/
DKconfig.debug35 # n, but then RMK will have to kill you ;).
/linux-4.4.14/drivers/staging/speakup/
Dspkguide.txt579 daemon is using /dev/softsynth. First, kill the daemon. Next, remove
/linux-4.4.14/arch/m68k/ifpsp060/src/
Dfpsp.S14399 andi.b &0x30,%d0 # kill precision