Searched refs:exited (Results 1 – 25 of 25) sorted by relevance
| /linux-4.4.14/tools/perf/tests/ |
| D | task-exit.c | 9 static int exited; variable
14 exited = 1; in sig_handler()
25 exited = 1; in workload_exec_failed_signal()
114 if (!exited || !nr_exit) { in test__task_exit()
|
| /linux-4.4.14/kernel/ |
| D | kthread.c | 46 struct completion exited; member
57 container_of(vfork, struct kthread, exited)
189 init_completion(&self.exited); in kthread()
191 current->vfork_done = &self.exited; in kthread()
492 wait_for_completion(&kthread->exited); in kthread_stop()
|
| /linux-4.4.14/scripts/gdb/linux/ |
| D | utils.py | 133 gdb.events.exited.disconnect(exit_handler)
155 gdb.events.exited.connect(exit_handler)
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,saw2.txt | 8 system, notifying them when a low power state is entered or exited.
|
| /linux-4.4.14/security/keys/ |
| D | Kconfig | 30 have exited, not that they survive the machine being rebooted.
|
| /linux-4.4.14/Documentation/vm/ |
| D | active_mm.txt | 55 user exited on another CPU while a lazy user was still active, so you do
|
| /linux-4.4.14/Documentation/RCU/ |
| D | rcu.txt | 33 three states, we know that that CPU has exited any previous RCU
|
| D | trace.txt | 325 exited immediately (without even being counted in nfqs above)
|
| /linux-4.4.14/Documentation/ia64/ |
| D | fsys.txt | 168 is exited. This is accomplished with the help of the lower-privilege
171 PSR.lp and returns immediately. When fsys-mode is exited via the
|
| /linux-4.4.14/Documentation/accounting/ |
| D | taskstats.txt | 130 the group is added up and added to the accumulated total for previously exited
|
| /linux-4.4.14/Documentation/ |
| D | robust-futexes.txt | 30 to be notified that the last owner of the lock exited in some irregular
|
| D | intel_txt.txt | 145 launch, TXT must first be exited. This is to prevent attacks that
|
| D | initrd.txt | 352 Once linuxrc exited, the kernel would mount again your initrd as root,
|
| /linux-4.4.14/Documentation/frv/ |
| D | features.txt | 302 context, i.e.: when the all the subscribing processes have exited or
|
| /linux-4.4.14/Documentation/locking/ |
| D | rt-mutex-design.txt | 438 If the task is not blocked on a mutex then the loop is exited. We are at
446 or timeout and has left the PI chain. In either case, the loop is exited, since
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | perf-script-python.txt | 92 don't care how it exited, so we'll use 'perf record' to record only
|
| /linux-4.4.14/tools/power/cpupower/po/ |
| D | de.po | 155 msgid "%s took %.5f seconds and exited with status %d\n"
|
| D | it.po | 155 msgid "%s took %.5f seconds and exited with status %d\n"
|
| D | cs.po | 158 msgid "%s took %.5f seconds and exited with status %d\n"
|
| D | fr.po | 155 msgid "%s took %.5f seconds and exited with status %d\n"
|
| D | pt.po | 153 msgid "%s took %.5f seconds and exited with status %d\n"
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | CHANGES | 666 wake up the demultiplex thread after it had exited. Do not log
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | proc.txt | 1709 skipped, especially if they've exited right after we printed their
|
| /linux-4.4.14/Documentation/networking/ |
| D | ip-sysctl.txt | 379 pressure mode, which is exited when memory consumption falls
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | api.txt | 3091 If exit_reason is KVM_EXIT_UNKNOWN, the vcpu has exited due to unknown
|