Lines Matching full:interrupted

194 …t-end delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end s…
200 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
206 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
212 …he front-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end s…
230 …-end delivered no uops for a period of at least 2 cycles which was not interrupted by a back-end s…
236 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
242 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
248 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
260 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
272 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
278 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
284 …e front-end delivered no uops for a period of 512 cycles which was not interrupted by a back-end s…
290 …e front-end delivered no uops for a period of 512 cycles which was not interrupted by a back-end s…
296 …he front-end delivered no uops for a period of 64 cycles which was not interrupted by a back-end s…
302 …he front-end delivered no uops for a period of 64 cycles which was not interrupted by a back-end s…
308 …the front-end delivered no uops for a period of 8 cycles which was not interrupted by a back-end s…