Searched full:exit (Results 1 – 25 of 248) sorted by relevance
12345678910
| /Documentation/translations/zh_CN/dev-tools/ |
| D | kcov.rst | 81 perror("open"), exit(1);
84 perror("ioctl"), exit(1);
89 perror("mmap"), exit(1);
92 perror("ioctl"), exit(1);
105 perror("ioctl"), exit(1);
108 perror("munmap"), exit(1);
110 perror("close"), exit(1);
170 perror("open"), exit(1);
172 perror("ioctl"), exit(1);
180 perror("mmap"), exit(1);
[all …]
|
| /Documentation/trace/ |
| D | fprobe.rst | 4 Fprobe - Function entry/exit probe
12 Fprobe is a function entry/exit probe mechanism based on ftrace.
14 on function entry and exit, similar to the kprobes and kretprobes, you can
23 attach callbacks to multiple function entry and exit. User needs to set up
83 Also, the unregister_fprobe() will guarantee that the both enter and exit
87 The fprobe entry/exit handler
90 The prototype of the entry/exit callback function are as follows:
98 Note that the @entry_ip is saved at function entry and passed to exit handler.
99 If the entry callback function returns !0, the corresponding exit callback will be cancelled.
107 This is the ftrace address of the traced function (both entry and exit).
[all …]
|
| D | ring-buffer-map.rst | 74 exit(EXIT_FAILURE);
78 exit(EXIT_FAILURE);
91 exit(EXIT_FAILURE);
94 exit(EXIT_FAILURE);
|
| /Documentation/admin-guide/hw-vuln/ |
| D | vmscape.rst | 39 IBPB before the first exit to userspace after VM-exit. If userspace did not run
40 between VM-exit and the next VM-entry, no IBPB is issued.
45 context switch time, while the userspace VMM can run after a VM-exit without a
83 * 'Mitigation: IBPB before exit to userspace':
87 exit to userspace after VM-exit.
91 IBPB is issued on every VM-exit. This occurs when other mitigations like
92 RETBLEED or SRSO are already issuing IBPB on VM-exit.
|
| /Documentation/core-api/ |
| D | entry.rst | 1 Entry/exit handling for exceptions, interrupts, syscalls and KVM
22 for entry code before RCU starts watching and exit code after RCU stops
55 All non-instrumentable entry/exit code sections before and after the RCU
106 exit_to_user_mode() is called last on exit.
116 guest and returns to the kernel on exit.
126 Do not nest KVM entry/exit transitions because doing so is nonsensical.
131 Interrupts entry and exit handling is slightly more complex than syscalls
135 and exit handling is exactly the same as for syscalls.
138 exit handling is slightly different. RCU state is only updated when the
188 disabled, interrupt nesting is common from an entry/exit perspective. For
[all …]
|
| /Documentation/dev-tools/ |
| D | kcov.rst | 81 perror("open"), exit(1);
84 perror("ioctl"), exit(1);
89 perror("mmap"), exit(1);
92 perror("ioctl"), exit(1);
105 perror("ioctl"), exit(1);
108 perror("munmap"), exit(1);
110 perror("close"), exit(1);
171 perror("open"), exit(1);
173 perror("ioctl"), exit(1);
181 perror("mmap"), exit(1);
[all …]
|
| D | sparse.rst | 62 regard to the annotated function's entry and exit.
64 __must_hold - The specified lock is held on function entry and exit.
66 __acquires - The specified lock is held on function exit, but not entry.
68 __releases - The specified lock is held on function entry, but not exit.
|
| /Documentation/userspace-api/media/v4l/ |
| D | selection-api-examples.rst | 22 exit(-1);
26 exit(-1);
44 exit(-1);
55 exit(-1);
77 exit(-1);
80 exit(-1);
|
| D | standard.rst | 84 exit(EXIT_FAILURE);
93 exit(EXIT_SUCCESS);
104 exit(EXIT_FAILURE);
119 exit(EXIT_FAILURE);
124 exit(EXIT_FAILURE);
144 exit(EXIT_FAILURE);
159 exit(EXIT_FAILURE);
164 exit(EXIT_FAILURE);
169 exit(EXIT_FAILURE);
179 exit(EXIT_FAILURE);
|
| D | capture.c.rst | 60 exit(EXIT_FAILURE);
205 exit(EXIT_FAILURE);
311 exit(EXIT_FAILURE);
319 exit(EXIT_FAILURE);
337 exit(EXIT_FAILURE);
346 exit(EXIT_FAILURE);
353 exit(EXIT_FAILURE);
395 exit(EXIT_FAILURE);
405 exit(EXIT_FAILURE);
414 exit(EXIT_FAILURE);
[all …]
|
| D | mmap.rst | 79 exit(EXIT_FAILURE);
87 exit(EXIT_FAILURE);
103 exit(EXIT_FAILURE);
114 /* If you do not exit here you should unmap() and free()
117 exit(EXIT_FAILURE);
152 exit(EXIT_FAILURE);
160 exit(EXIT_FAILURE);
181 exit(EXIT_FAILURE);
194 /* If you do not exit here you should unmap() and free()
197 exit(EXIT_FAILURE);
|
| D | v4l2grab.c.rst | 50 exit(EXIT_FAILURE);
72 exit(EXIT_FAILURE);
84 exit(EXIT_FAILURE);
113 exit(EXIT_FAILURE);
152 exit(EXIT_FAILURE);
|
| D | video.rst | 42 exit(EXIT_FAILURE);
50 exit(EXIT_FAILURE);
67 exit(EXIT_FAILURE);
|
| D | crop.rst | 177 exit (EXIT_FAILURE);
189 exit (EXIT_FAILURE);
215 exit (EXIT_FAILURE);
236 exit (EXIT_FAILURE);
257 exit (EXIT_FAILURE);
279 exit (EXIT_FAILURE);
288 exit (EXIT_FAILURE);
300 exit (EXIT_FAILURE);
|
| /Documentation/devicetree/bindings/power/ |
| D | domain-idle-state.yaml | 34 state. Note that, the exit-latency-us duration may be guaranteed only
37 exit-latency-us:
39 The worst case latency in microseconds required to exit the idle
60 - exit-latency-us
72 exit-latency-us = <40>;
|
| /Documentation/devicetree/bindings/cpu/ |
| D | idle-states.yaml | 23 parameters required to enter/exit specific idle states on a given processor.
72 triggered upon idle states entry and exit.
75 properties required to enter and exit an idle state:
77 ..__[EXEC]__|__[PREP]__|__[ENTRY]__|__[IDLE]__|__[EXIT]__|__[EXEC]__..
82 |<- exit ->|
94 (i.e. less than the ENTRY + EXIT duration). If aborted, CPU
104 EXIT: Period during which the CPU is brought back to operational
108 exit-latency may be guaranteed only after entry-latency has passed.
115 to be entry-latency + exit-latency.
127 wakeup-delay = exit-latency + max(entry-latency - (now - entry-timestamp), 0)
[all …]
|
| /Documentation/locking/ |
| D | robust-futex-ABI.rst | 9 futexes, for kernel assist of cleanup of held locks on task exit.
19 2) internal kernel code at exit, to handle any listed locks held
32 to do so, then improperly listed locks will not be cleaned up on exit,
52 exit, if the corresponding sys_set_robust_list() call has been made to
70 and is needed to correctly resolve races should a thread exit while
82 waiting for a lock on a threads exit if that next thread used the futex
86 robust_futex support for exit cleanup of that lock, it should have one
114 up locks held at the time of (a perhaps unexpectedly) exit.
120 list 'head' is, and to walk the list on thread exit, handling locks
156 On exit, the kernel will consider the address stored in
[all …]
|
| /Documentation/arch/s390/ |
| D | config3270.sh | 33 ls $P > /dev/null 2>&1 || exit 1
37 echo "#!/bin/sh" > $SCR || exit 1
43 echo "grep -v $TTY $INITTAB > $NINITTAB" > $SCRTMP || exit 1
72 echo mv $INITTAB $OINITTAB >> $SCRTMP || exit 1
76 exit 0
|
| /Documentation/arch/x86/ |
| D | pti.rst | 21 data: only what is needed to enter/exit the kernel such as the
22 entry/exit functions themselves and the interrupt descriptor table
47 and exit the kernel. This data is entirely contained in the 'struct
81 and exit (it can be skipped when the kernel is interrupted,
83 cycles, and are required at every entry and exit.
97 switch, or kernel entry/exit) cheaper. But, on systems with
100 deferred until the exit to userspace, minimizing the cost.
107 and one for the entry/exit structures. At fork(), we need to
146 in /proc/interrupts). This exercises the NMI entry/exit code which
178 * Kernel crashes at the first exit to userspace. entry_64.S
[all …]
|
| /Documentation/devicetree/bindings/thermal/ |
| D | thermal-idle.yaml | 38 exit-latency-us:
40 The exit latency constraint in microsecond for the injected idle state
78 exit-latency-us = <500>;
94 exit-latency-us = <500>;
|
| /Documentation/admin-guide/aoe/ |
| D | udev-install.sh | 17 exit 1
31 exit 1
|
| /Documentation/arch/arm/samsung/ |
| D | clksrc-change-registers.awk | 45 exit
53 exit
63 exit
100 exit 1;
|
| /Documentation/bpf/standardization/ |
| D | abi.rst | 19 * R0: return value from function calls, and exit value for BPF programs
28 ``EXIT``.
|
| /Documentation/usb/ |
| D | usbdevfs-drop-permissions.c | 84 "[0] Exit now\n" in main()
93 goto exit; in main()
112 exit: in main()
|
| /Documentation/accounting/ |
| D | taskstats.rst | 11 - efficiently provide statistics during lifetime of a task and on its exit
49 send commands and process responses, listen for per-tid/tgid exit data,
83 Commands to register/deregister interest in exit data from a set of cpus
87 comma-separated cpu ranges e.g. to listen to exit data from cpus 1,2,3,5,7,8
164 up with the kernel's rate of sending per-tid/tgid exit data leading to data
171 listeners to receive exit data.
|
12345678910