Home
last modified time | relevance | path

Searched refs:caught (Results 1 – 25 of 25) sorted by relevance

/linux-4.4.14/fs/proc/
Darray.c260 sigset_t pending, shpending, blocked, ignored, caught; in task_sig() local
269 sigemptyset(&caught); in task_sig()
275 collect_sigign_sigcatch(p, &ignored, &caught); in task_sig()
292 render_sigset_t(m, "SigCgt:\t", &caught); in task_sig()
/linux-4.4.14/sound/parisc/
Dharmony.c502 unsigned long caught; in snd_harmony_capture_pointer() local
511 caught = rcuradd - h->cbuf.addr; in snd_harmony_capture_pointer()
515 rcuradd, h->cbuf.addr, caught); in snd_harmony_capture_pointer()
522 return bytes_to_frames(rt, caught); in snd_harmony_capture_pointer()
/linux-4.4.14/Documentation/cgroups/
Dfreezer-subsystem.txt21 from within the tasks we wish to freeze. While SIGSTOP cannot be caught,
23 SIGCONT is especially unsuitable since it can be caught by the task. Any
/linux-4.4.14/drivers/staging/speakup/
DDefaultKeyAssignments44 synth until it has caught up with what is being printed on the
/linux-4.4.14/Documentation/arm/
Dmemory.txt79 space are also caught via this mapping.
DPorting104 of the mapped memory map) to be caught. Normally set to 8MB.
/linux-4.4.14/Documentation/device-mapper/
Dlog-writes.txt51 which isn't quite what happened and wouldn't be caught during the log replay.
/linux-4.4.14/arch/arm/plat-samsung/
DKconfig60 one bank to another to be caught, at the expense of using a little
/linux-4.4.14/Documentation/trace/
Dmmiotrace.txt105 are not caught, since the mapping always exists and is returned directly.
/linux-4.4.14/Documentation/scsi/
Din2000.txt106 a few people downloaded before I caught it - could have
Dst.txt91 are caught at that point, but this takes time. In some applications, several
/linux-4.4.14/Documentation/frv/
Dfeatures.txt100 inaccessible so that NULL pointer errors can be caught; and (2) the bottom
/linux-4.4.14/Documentation/development-process/
D4.Coding212 automated way. Any problem caught by the computer is a problem which will
393 ensure that code which has not been updated is caught by the compiler.
/linux-4.4.14/Documentation/locking/
Dww-mutex-design.txt320 as possible. Some common api abuses will be caught with
/linux-4.4.14/Documentation/virtual/kvm/
Dtimekeeping.txt555 delivered, and after which, the guest time may need to be caught up. NTP may
565 always be caught up to the original rate. KVM clock avoids these problems by
/linux-4.4.14/Documentation/hwmon/
Dsysfs-interface59 between readings to be caught and alarmed. The exact definition of an
/linux-4.4.14/arch/m68k/ifpsp060/src/
Dpfpsp.S3160 # exceptions, they won't pass through here since they are caught
3718 # exceptions, they won't pass through here since they are caught
Dfpsp.S3161 # exceptions, they won't pass through here since they are caught
3719 # exceptions, they won't pass through here since they are caught
6640 # not be caught until gen_except(). Now, with the exceptions being
Dfplsp.S9270 # exception to be put into the machine which will be caught and corrected
/linux-4.4.14/Documentation/filesystems/
Dproc.txt249 SigCgt bitmap of caught signals
315 sigcatch bitmap of caught signals
/linux-4.4.14/lib/
DKconfig.debug686 points; some don't and need to be caught.
/linux-4.4.14/Documentation/power/
Dpci.txt199 putting the device into a low-power state, have to be caught and handled as
/linux-4.4.14/drivers/scsi/aic7xxx/
Daic79xx.seq73 * If the kernel has caught up with us, thaw the queue.
/linux-4.4.14/Documentation/networking/
Dip-sysctl.txt775 ip_options_compile(). Either way is "safe" as errors are caught else
/linux-4.4.14/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt3468 caught by the signal thread, which detaches the process: