interrupted (full) in projects: linux - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:interrupted (Results 1 – 25 of 494) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...20

/linux/tools/perf/pmu-events/arch/x86/rocketlake/
H A D	frontend.json	102 "PublicDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end stall.", 107 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end stall.", 113 "PublicDescription": "Counts retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end stall.", 118 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end stall.", 135 "PublicDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end stall.", 140 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end stall.", 146 "PublicDescription": "Counts retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end stall.", 151 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end stall.", 162 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end stall.", 173 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 4 cycles which was not interrupted b [all...]
/linux/tools/perf/pmu-events/arch/x86/icelakex/
H A D	frontend.json	102 "PublicDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end stall.", 107 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end stall.", 113 "PublicDescription": "Counts retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end stall.", 118 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end stall.", 135 "PublicDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end stall.", 140 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end stall.", 146 "PublicDescription": "Counts retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end stall.", 151 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end stall.", 162 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end stall.", 173 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 4 cycles which was not interrupted b [all...]
/linux/tools/perf/pmu-events/arch/x86/tigerlake/
H A D	frontend.json	102 "PublicDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end stall.", 107 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end stall.", 113 "PublicDescription": "Counts retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end stall.", 118 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end stall.", 135 "PublicDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end stall.", 140 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end stall.", 146 "PublicDescription": "Counts retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end stall.", 151 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end stall.", 162 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end stall.", 173 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 4 cycles which was not interrupted b [all...]
/linux/tools/perf/pmu-events/arch/x86/icelake/
H A D	frontend.json	102 "PublicDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end stall.", 107 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end stall.", 113 "PublicDescription": "Counts retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end stall.", 118 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end stall.", 135 "PublicDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end stall.", 140 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end stall.", 146 "PublicDescription": "Counts retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end stall.", 151 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end stall.", 162 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end stall.", 173 "BriefDescription": "Retired instructions that are fetched after an interval where the front-end delivered no uops for a period of 4 cycles which was not interrupted b [all...]
/linux/tools/perf/pmu-events/arch/x86/emeraldrapids/
H A 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/tools/perf/pmu-events/arch/x86/sapphirerapids/
H A 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/tools/perf/pmu-events/arch/x86/graniterapids/
H A D	frontend.json	122 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s… 127 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s… 133 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s… 138 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s… 155 …-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… 171 …-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… 193 …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	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/include/net/
H A D	strparser.h	`36 unsigned int interrupted; member 97 u32 interrupted : 1; member 136 if (strp->interrupted) in save_strp_stats() 137 agg_stats->interrupted++; in save_strp_stats() 154 SAVE_PSOCK_STATS(interrupted); in aggregate_strp_stats()`
/linux/tools/perf/pmu-events/arch/x86/meteorlake/
H A D	frontend.json	193 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s… 199 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s… 205 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s… 211 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s… 229 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s… 235 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s… 241 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s… 247 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s… 259 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s… 271 …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/pantherlake/
H A D	frontend.json	170 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s… 176 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s… 182 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s… 200 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s… 206 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s… 212 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s… 218 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s… 230 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s… 242 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s… 248 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s… [all …]
/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/tools/perf/pmu-events/arch/x86/lunarlake/
H A 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/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/kernel/sched/
H A D	completion.c	`217 * Return: -ERESTARTSYS if interrupted, 0 if completed. 237 * Return: -ERESTARTSYS if interrupted, 0 if timed out, positive (at least 1, 253 * interrupted by a kill signal. 255 * Return: -ERESTARTSYS if interrupted, 0 if completed. 284 * interrupted by a kill signal. The timeout is in jiffies. 286 * Return: -ERESTARTSYS if interrupted, 0 if timed out, positive (at least 1,`
/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/tools/perf/pmu-events/arch/x86/arrowlake/
H A D	frontend.json	305 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s… 311 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s… 317 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s… 335 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s… 341 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s… 347 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s… 353 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s… 365 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s… 377 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s… 383 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s… [all …]
/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/kernel/locking/
H A D	semaphore.c	`106 * down_interruptible - acquire the semaphore unless interrupted 111 * If the sleep is interrupted by a signal, this function will return -EINTR. 137 * If the sleep is interrupted by a fatal signal, this function will return 263 goto interrupted; in ___down_common() 280 interrupted: in ___down_common()`
/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/xen/interface/
H A D	xenpmu.h	`72 /* Interrupted VCPU / 82 Domain that was interrupted. On non-privileged guests set to`
/linux/include/linux/
H A D	wait.h	498 * The function will return -ERESTARTSYS if it was interrupted by a 533 * interrupted by a signal. 610 * interrupted by a signal, or -ETIME if the timeout elapsed. 816 * The function will return -ERESTARTSYS if it was interrupted by a 843 * The function will return -ERESTARTSYS if it was interrupted by a 874 * The function will return -ERESTARTSYS if it was interrupted by a 905 * The function will return -ERESTARTSYS if it was interrupted by a 928 * The function will return -ERESTARTSYS if it was interrupted by a 956 * The function will return -ERESTARTSYS if it was interrupted by a signal 1003 * interrupted by a kill signal. [all …]

12 3 4 5 6 7 8 9 10 >>...20