Lines Matching full:interrupted

109 …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…
124 …e front-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end s…
130 …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…
169 …e front-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end s…
175 …-end had at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end s…
190 …he front-end delivered no uops for a period of 32 cycles which was not interrupted by a back-end s…
205 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
214 …the front-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end s…
220 …e front-end delivered no uops for a period of 512 cycles which was not interrupted by a back-end s…
229 …e front-end delivered no uops for a period of 512 cycles which was not interrupted by a back-end s…
235 …he front-end delivered no uops for a period of 64 cycles which was not interrupted by a back-end s…
244 …he front-end delivered no uops for a period of 64 cycles which was not interrupted by a back-end s…
250 …the front-end delivered no uops for a period of 8 cycles which was not interrupted by a back-end s…