| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
| D | frontend.json | 95 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
100 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
106 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
111 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
128 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
133 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
139 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
144 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
155 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
166 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/icelakex/ |
| D | frontend.json | 98 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
103 …e front-end delivered no uops for a period of 128 cycles 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…
114 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
131 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
136 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
142 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
147 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
158 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
169 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/rocketlake/ |
| D | frontend.json | 98 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
103 …e front-end delivered no uops for a period of 128 cycles 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…
114 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
131 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
136 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
142 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
147 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
158 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
169 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/tigerlake/ |
| D | frontend.json | 98 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
103 …e front-end delivered no uops for a period of 128 cycles 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…
114 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
131 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
136 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
142 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
147 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
158 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
169 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/alderlake/ |
| D | frontend.json | 113 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
119 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
125 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
131 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
149 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
155 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
161 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
167 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
179 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
191 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/icelake/ |
| D | frontend.json | 98 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
103 …e front-end delivered no uops for a period of 128 cycles 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…
114 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
131 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
136 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
142 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
147 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
158 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
169 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /kernel/liteos_a/testsuites/unittest/libc/time/timer/smoke/ |
| D | timer_test_002.cpp | 56 LogPrintln("sleep %ds", 3); // 3, this sleep may be interrupted by the timer in TimerTest()
57 sleep(3); // 3, this sleep may be interrupted by the timer in TimerTest()
61 LogPrintln("sleep %ds", 2); // 2, this sleep may be interrupted by the timer in TimerTest()
62 sleep(2); // 2, this sleep may be interrupted by the timer in TimerTest()
66 LogPrintln("sleep %ds", 2); // 2, this sleep may be interrupted by the timer in TimerTest()
67 sleep(2); // 2, this sleep may be interrupted by the timer in TimerTest()
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/icelake/ |
| D | frontend.json | 277 …the front-end delivered no uops for a period of 2 cycles which was not interrupted by a back-end s…
286 …the front-end delivered no uops for a period of 2 cycles which was not interrupted by a back-end s…
292 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
301 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
316 …the front-end delivered no uops for a period of 8 cycles which was not interrupted by a back-end s…
331 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
346 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
352 …he front-end delivered no uops for a period of 64 cycles which was not interrupted by a back-end s…
361 …he front-end delivered no uops for a period of 64 cycles which was not interrupted by a back-end s…
367 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/meteorlake/ |
| D | frontend.json | 142 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
148 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
154 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
160 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
178 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
184 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
190 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
196 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
208 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
220 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /kernel/linux/linux-5.10/include/net/ |
| D | strparser.h | 36 unsigned int interrupted; member
84 u32 interrupted : 1; member
125 if (strp->interrupted) in save_strp_stats()
126 agg_stats->interrupted++; in save_strp_stats()
143 SAVE_PSOCK_STATS(interrupted); in aggregate_strp_stats()
|
| /kernel/linux/linux-6.6/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()
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| D | frontend.json | 94 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
99 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
109 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
120 …the front-end delivered no uops for a period of 2 cycles which was not interrupted by a back-end s…
130 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
140 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
151 …end had at least 2 bubble-slots for a period of 2 cycles which was not interrupted by a back-end s…
161 …end had at least 3 bubble-slots for a period of 2 cycles which was not interrupted by a back-end s…
171 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
182 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/skylake/ |
| D | frontend.json | 94 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
99 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
109 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
120 …the front-end delivered no uops for a period of 2 cycles which was not interrupted by a back-end s…
130 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
140 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
151 …end had at least 2 bubble-slots for a period of 2 cycles which was not interrupted by a back-end s…
161 …end had at least 3 bubble-slots for a period of 2 cycles which was not interrupted by a back-end s…
171 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
182 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/skylakex/ |
| D | frontend.json | 94 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
99 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
109 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
120 …the front-end delivered no uops for a period of 2 cycles which was not interrupted by a back-end s…
130 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
140 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
151 …end had at least 2 bubble-slots for a period of 2 cycles which was not interrupted by a back-end s…
161 …end had at least 3 bubble-slots for a period of 2 cycles which was not interrupted by a back-end s…
171 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
182 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /kernel/linux/linux-6.6/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()
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/skylake/ |
| D | frontend.json | 331 …the front-end delivered no uops for a period of 2 cycles which was not interrupted by a back-end s…
344 …end had at least 2 bubble-slots for a period of 2 cycles which was not interrupted by a back-end s…
357 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
371 …the front-end delivered no uops for a period of 8 cycles which was not interrupted by a back-end s…
385 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
399 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
412 …he front-end delivered no uops for a period of 64 cycles which was not interrupted by a back-end s…
425 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
438 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
451 …e front-end delivered no uops for a period of 512 cycles which was not interrupted by a back-end s…
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/skylakex/ |
| D | frontend.json | 27 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
108 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
210 …he front-end delivered no uops for a period of 64 cycles which was not interrupted by a back-end s…
297 …e front-end delivered no uops for a period of 512 cycles which was not interrupted by a back-end s…
310 …the front-end delivered no uops for a period of 8 cycles which was not interrupted by a back-end s…
332 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
338 …the front-end delivered no uops for a period of 2 cycles which was not interrupted by a back-end s…
351 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
396 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
409 …end had at least 2 bubble-slots for a period of 2 cycles which was not interrupted by a back-end s…
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| D | frontend.json | 37 …end had at least 2 bubble-slots for a period of 2 cycles which was not interrupted by a back-end s…
50 …end had at least 3 bubble-slots for a period of 2 cycles which was not interrupted by a back-end s…
63 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
199 …the front-end delivered no uops for a period of 8 cycles which was not interrupted by a back-end s…
213 …the front-end delivered no uops for a period of 2 cycles which was not interrupted by a back-end s…
226 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
268 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
283 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
316 …he front-end delivered no uops for a period of 64 cycles which was not interrupted by a back-end s…
353 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/vmwgfx/ |
| D | ttm_lock.h | 102 * -ERESTARTSYS If interrupted by a signal and interruptible is true.
119 * -ERESTARTSYS If interrupted by a signal and interruptible is true.
140 * -ERESTARTSYS If interrupted by a signal and interruptible is true.
180 * -ERESTARTSYS If interrupted by a signal and interruptible is true.
214 * -ERESTARTSYS If interrupted by a signal and interruptible is true.
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-5.10/kernel/locking/ |
| D | semaphore.c | 67 * down_interruptible - acquire the semaphore unless interrupted
72 * If the sleep is interrupted by a signal, this function will return -EINTR.
97 * If the sleep is interrupted by a fatal signal, this function will return
215 goto interrupted; in __down_common()
230 interrupted: in __down_common()
|
| /kernel/linux/linux-6.6/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,
|
| /kernel/linux/linux-5.10/kernel/sched/ |
| D | completion.c | 202 * Return: -ERESTARTSYS if interrupted, 0 if completed.
221 * Return: -ERESTARTSYS if interrupted, 0 if timed out, positive (at least 1,
237 * interrupted by a kill signal.
239 * Return: -ERESTARTSYS if interrupted, 0 if completed.
257 * interrupted by a kill signal. The timeout is in jiffies.
259 * Return: -ERESTARTSYS if interrupted, 0 if timed out, positive (at least 1,
|
| /kernel/linux/linux-6.6/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()
|