| /linux/tools/perf/pmu-events/arch/x86/rocketlake/ |
| H A D | frontend.json | 108 …t-end delivered no uops for a period of at least 1 cycle 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…
120 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
125 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
144 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
149 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
156 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
161 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
173 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
185 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/icelakex/ |
| H A D | frontend.json | 108 …t-end delivered no uops for a period of at least 1 cycle 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…
120 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
125 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
144 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
149 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
156 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
161 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
173 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
185 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/tigerlake/ |
| H A D | frontend.json | 108 …t-end delivered no uops for a period of at least 1 cycle 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…
120 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
125 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
144 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
149 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
156 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
161 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
173 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
185 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/icelake/ |
| H A D | frontend.json | 108 …t-end delivered no uops for a period of at least 1 cycle 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…
120 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
125 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
144 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
149 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
156 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
161 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
173 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
185 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/graniterapids/ |
| H A D | frontend.json | 117 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
122 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
129 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
134 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
153 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
158 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
165 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
170 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
182 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
194 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
| H A D | frontend.json | 105 …t-end delivered no uops for a period of at least 1 cycle 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…
117 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
122 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
141 …-end delivered no uops for a period of at least 2 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…
153 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
158 …-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…
182 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/emeraldrapids/ |
| H A D | frontend.json | 105 …t-end delivered no uops for a period of at least 1 cycle 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…
117 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
122 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
141 …-end delivered no uops for a period of at least 2 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…
153 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
158 …-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…
182 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/meteorlake/ |
| H A D | frontend.json | 146 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
152 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
159 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
165 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
185 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
191 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
198 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
204 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
217 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
230 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/alderlake/ |
| H A D | frontend.json | 124 …t-end delivered no uops for a period of at least 1 cycle 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…
137 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
143 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
163 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
169 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
176 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
182 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
195 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
208 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
[all …]
|
| /linux/include/net/ |
| H A 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/fs/orangefs/ |
| H A 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/tools/perf/pmu-events/arch/x86/skylake/ |
| H A 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/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| H A 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/tools/perf/pmu-events/arch/x86/skylakex/ |
| H A 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/kernel/sched/ |
| H A 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/kernel/ |
| H A 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/tools/testing/selftests/net/ |
| H A 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/Documentation/arch/arm64/ |
| H A 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/crypto/ |
| H A 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/include/linux/mtd/ |
| H A 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.
|
| /linux/include/xen/interface/ |
| H A D | xenpmu.h | 72 /* Interrupted VCPU */
82 * Domain that was interrupted. On non-privileged guests set to
|
| /linux/drivers/media/platform/samsung/s5p-mfc/ |
| H A D | s5p_mfc_intr.c | 34 mfc_err("Interrupted by a signal\n"); in s5p_mfc_wait_for_done_dev()
72 mfc_err("Interrupted by a signal\n"); in s5p_mfc_wait_for_done_ctx()
|
| /linux/drivers/staging/gpib/nec7210/ |
| H A D | nec7210.c | 56 dev_dbg(board->gpib_dev, "gpib: parallel poll interrupted\n"); in nec7210_parallel_poll()
433 dev_dbg(board->gpib_dev, "gpib command wait interrupted\n"); in nec7210_command()
458 dev_dbg(board->gpib_dev, "gpib command wait interrupted\n"); in nec7210_command()
487 dev_dbg(board->gpib_dev, "nec7210: pio read wait interrupted\n"); in pio_read()
506 dev_dbg(board->gpib_dev, "interrupted by timeout\n"); in pio_read()
511 dev_dbg(board->gpib_dev, "interrupted by device clear\n"); in pio_read()
561 dev_dbg(board->gpib_dev, "nec7210: dma read wait interrupted\n"); in __dma_read()
642 dev_dbg(board->gpib_dev, "gpib write interrupted\n"); in pio_write_wait()
650 dev_dbg(board->gpib_dev, "nec7210: write interrupted by clear\n"); in pio_write_wait()
737 dev_dbg(board->gpib_dev, "gpib write interrupted!\n"); in __dma_write()
|
| /linux/tools/testing/selftests/connector/ |
| H A D | proc_filter.c | 28 volatile static int interrupted; variable
131 interrupted = 1; in sigint()
282 while (!interrupted) { in main()
|
| /linux/Documentation/i2c/ |
| H A D | i2c-protocol.rst | 61 Normally message is interrupted immediately if there is [NA] from the
95 like SCCB require that. Normally, you really don't want to get interrupted
|