| /linux-6.15/tools/perf/pmu-events/arch/x86/rocketlake/ |
| D | frontend.json | 102 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
107 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
113 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
118 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
135 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
140 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
146 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
151 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
162 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
173 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux-6.15/tools/perf/pmu-events/arch/x86/icelake/ |
| D | frontend.json | 102 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
107 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
113 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
118 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
135 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
140 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
146 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
151 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
162 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
173 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux-6.15/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
| D | frontend.json | 99 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
104 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
110 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
115 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
132 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
137 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
143 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
148 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
159 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
170 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux-6.15/tools/perf/pmu-events/arch/x86/emeraldrapids/ |
| D | frontend.json | 99 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
104 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
110 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
115 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
132 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
137 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
143 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
148 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
159 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
170 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux-6.15/tools/perf/pmu-events/arch/x86/tigerlake/ |
| D | frontend.json | 102 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
107 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
113 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
118 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
135 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
140 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
146 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
151 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
162 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
173 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux-6.15/tools/perf/pmu-events/arch/x86/icelakex/ |
| D | frontend.json | 102 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
107 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
113 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
118 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
135 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
140 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
146 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
151 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
162 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
173 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux-6.15/tools/perf/pmu-events/arch/x86/graniterapids/ |
| D | frontend.json | 110 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
115 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
121 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
126 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
143 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
148 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
154 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
159 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
170 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
181 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux-6.15/tools/perf/pmu-events/arch/x86/alderlake/ |
| D | frontend.json | 118 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
124 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
130 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
136 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
154 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
160 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
166 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
172 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
184 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
196 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux-6.15/tools/perf/pmu-events/arch/x86/meteorlake/ |
| D | frontend.json | 139 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
145 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
151 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
157 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
175 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
181 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
187 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
193 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
205 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
217 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux-6.15/include/net/ |
| D | strparser.h | 36 unsigned int interrupted; member
97 u32 interrupted : 1; member
138 if (strp->interrupted) in save_strp_stats()
139 agg_stats->interrupted++; in save_strp_stats()
156 SAVE_PSOCK_STATS(interrupted); in aggregate_strp_stats()
|
| /linux-6.15/fs/orangefs/ |
| D | waitqueue.c | 99 * check to see if we were interrupted while waiting for in service_operation()
105 "%s: service_operation interrupted.\n", in service_operation()
254 * handle interrupted cases depending on what state we were in when in orangefs_clean_up_interrupted_operation()
281 "Interrupted: Removed op %p from request_list\n", in orangefs_clean_up_interrupted_operation()
290 "Interrupted: Removed op %p" in orangefs_clean_up_interrupted_operation()
295 gossip_err("interrupted operation is in a weird state 0x%x\n", in orangefs_clean_up_interrupted_operation()
314 * or if we were interrupted.
348 "%s: operation interrupted, tag %llu, %p\n", in wait_for_matching_downcall()
|
| /linux-6.15/tools/perf/pmu-events/arch/x86/skylake/ |
| D | frontend.json | 104 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
109 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
120 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
132 …the front-end delivered no uops for a period of 2 cycles which was not interrupted by a back-end s…
143 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
154 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
166 …end had at least 2 bubble-slots for a period of 2 cycles which was not interrupted by a back-end s…
177 …end had at least 3 bubble-slots for a period of 2 cycles which was not interrupted by a back-end s…
188 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
200 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux-6.15/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| D | frontend.json | 104 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
109 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
120 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
132 …the front-end delivered no uops for a period of 2 cycles which was not interrupted by a back-end s…
143 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
154 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
166 …end had at least 2 bubble-slots for a period of 2 cycles which was not interrupted by a back-end s…
177 …end had at least 3 bubble-slots for a period of 2 cycles which was not interrupted by a back-end s…
188 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
200 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux-6.15/tools/perf/pmu-events/arch/x86/skylakex/ |
| D | frontend.json | 104 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
109 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
120 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
132 …the front-end delivered no uops for a period of 2 cycles which was not interrupted by a back-end s…
143 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
154 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
166 …end had at least 2 bubble-slots for a period of 2 cycles which was not interrupted by a back-end s…
177 …end had at least 3 bubble-slots for a period of 2 cycles which was not interrupted by a back-end s…
188 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
200 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux-6.15/tools/perf/pmu-events/arch/x86/arrowlake/ |
| D | frontend.json | 161 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
167 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
173 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
191 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
197 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
203 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
209 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
221 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
233 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
239 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux-6.15/tools/perf/pmu-events/arch/x86/lunarlake/ |
| D | frontend.json | 232 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
238 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
244 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
262 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
268 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
274 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
280 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
292 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
304 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
310 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux-6.15/kernel/ |
| D | cpu_pm.c | 103 * timers context save/restore which shouldn't be interrupted. Hence it
122 * shouldn't be interrupted. Hence it must be called with interrupts disabled.
142 * shouldn't be interrupted. Hence it must be called with interrupts disabled.
165 * shouldn't be interrupted. Hence it must be called with interrupts disabled.
|
| /linux-6.15/kernel/sched/ |
| D | completion.c | 212 * Return: -ERESTARTSYS if interrupted, 0 if completed.
232 * Return: -ERESTARTSYS if interrupted, 0 if timed out, positive (at least 1,
248 * interrupted by a kill signal.
250 * Return: -ERESTARTSYS if interrupted, 0 if completed.
279 * interrupted by a kill signal. The timeout is in jiffies.
281 * Return: -ERESTARTSYS if interrupted, 0 if timed out, positive (at least 1,
|
| /linux-6.15/kernel/locking/ |
| D | semaphore.c | 70 * down_interruptible - acquire the semaphore unless interrupted
75 * If the sleep is interrupted by a signal, this function will return -EINTR.
101 * If the sleep is interrupted by a fatal signal, this function will return
224 goto interrupted; in ___down_common()
239 interrupted: in ___down_common()
|
| /linux-6.15/tools/testing/selftests/net/ |
| D | udpgso_bench_rx.c | 52 static bool interrupted; variable
58 interrupted = true; in sigint_handler()
103 if (interrupted) in do_poll()
113 interrupted = true; in do_poll()
151 if (interrupted) in do_socket()
390 } while (!interrupted); in do_recv()
|
| /linux-6.15/Documentation/arch/arm64/ |
| D | gcs.rst | 155 pointer for the interrupted context on signal delivery. This will always
159 for the interrupted context as PR_GET_SHADOW_STACK_STATUS would.
161 * The signal handler is run with the same GCS configuration as the interrupted
164 * When GCS is enabled for the interrupted thread a signal handling specific
169 * The signal handler will use the same GCS as the interrupted context.
|
| /linux-6.15/crypto/ |
| D | aes_ti.c | 27 * evicted when the CPU is interrupted to do something else. in aesti_encrypt()
43 * evicted when the CPU is interrupted to do something else. in aesti_decrypt()
|
| /linux-6.15/include/linux/ |
| D | wait.h | 496 * The function will return -ERESTARTSYS if it was interrupted by a
531 * interrupted by a signal.
608 * interrupted by a signal, or -ETIME if the timeout elapsed.
814 * The function will return -ERESTARTSYS if it was interrupted by a
841 * The function will return -ERESTARTSYS if it was interrupted by a
872 * The function will return -ERESTARTSYS if it was interrupted by a
903 * The function will return -ERESTARTSYS if it was interrupted by a
926 * The function will return -ERESTARTSYS if it was interrupted by a
954 * The function will return -ERESTARTSYS if it was interrupted by a signal
989 * interrupted by a kill signal.
[all …]
|
| /linux-6.15/include/xen/interface/ |
| D | xenpmu.h | 72 /* Interrupted VCPU */
82 * Domain that was interrupted. On non-privileged guests set to
|
| /linux-6.15/include/linux/mtd/ |
| D | ubi.h | 63 * The @upd_marker flag is set if the volume update operation was interrupted.
66 * further interrupted, the update marker indicates this. If the update marker
73 * reasons, but not because an interrupted volume update
75 * interrupted update operation.
|