powerpc/power8/marked.json

35 …another chip's L2 or L3 on a different Node or Group (Distant), as this chip due to a marked load",
41 …another chip's L2 or L3 on a different Node or Group (Distant), as this chip due to a marked load",
47 …another chip's L2 or L3 on a different Node or Group (Distant), as this chip due to a marked load",
53 …another chip's L2 or L3 on a different Node or Group (Distant), as this chip due to a marked load",
59 …e was reloaded from another chip's L4 on a different Node or Group (Distant) due to a marked load",
65 …cles to reload from another chip's L4 on a different Node or Group (Distant) due to a marked load",
71 … was reloaded from another chip's memory on the same Node or Group (Distant) due to a marked load",
77 …les to reload from another chip's memory on the same Node or Group (Distant) due to a marked load",
83 …"BriefDescription": "The processor's data cache was reloaded from local core's L2 due to a marked …
95 …"Duration in cycles to reload from a location other than the local core's L2 due to a marked load",
101     "BriefDescription": "Duration in cycles to reload from local core's L2 due to a marked load",
107 …'s data cache was reloaded from local core's L2 with load hit store conflict due to a marked load",
113 …ration in cycles to reload from local core's L2 with load hit store conflict due to a marked load",
119 …cessor's data cache was reloaded from local core's L2 with dispatch conflict due to a marked load",
125 …": "Duration in cycles to reload from local core's L2 with dispatch conflict due to a marked load",
131 … reloaded from local core's L2 hit without dispatch conflicts on Mepf state. due to a marked load",
137 …to reload from local core's L2 hit without dispatch conflicts on Mepf state. due to a marked load",
143 …he processor's data cache was reloaded from local core's L2 without conflict due to a marked load",
149 …"BriefDescription": "Duration in cycles to reload from local core's L2 without conflict due to a m…
155 …"BriefDescription": "The processor's data cache was reloaded from local core's L3 due to a marked …
161 …sor's data cache was reloaded from a location other than the local core's L3 due to a marked load",
167 …"Duration in cycles to reload from a location other than the local core's L3 due to a marked load",
173     "BriefDescription": "Duration in cycles to reload from local core's L3 due to a marked load",
179 …cessor's data cache was reloaded from local core's L3 with dispatch conflict due to a marked load",
185 …": "Duration in cycles to reload from local core's L3 with dispatch conflict due to a marked load",
191 … reloaded from local core's L3 without dispatch conflicts hit on Mepf state. due to a marked load",
197 …to reload from local core's L3 without dispatch conflicts hit on Mepf state. due to a marked load",
203 …he processor's data cache was reloaded from local core's L3 without conflict due to a marked load",
209 …"BriefDescription": "Duration in cycles to reload from local core's L3 without conflict due to a m…
215 …"BriefDescription": "The processor's data cache was reloaded from the local chip's L4 cache due to…
221 …"BriefDescription": "Duration in cycles to reload from the local chip's L4 cache due to a marked l…
227 …"BriefDescription": "The processor's data cache was reloaded from the local chip's Memory due to a…
233 …"BriefDescription": "Duration in cycles to reload from the local chip's Memory due to a marked loa…
239 …as reloaded from a memory location including L4 from local remote or distant due to a marked load",
245 …s to reload from a memory location including L4 from local remote or distant due to a marked load",
251 …ified data from another core's L2/L3 on a different chip (remote or distant) due to a marked load",
257 …ified data from another core's L2/L3 on a different chip (remote or distant) due to a marked load",
263 …ed either shared or modified data from another core's L2/L3 on the same chip due to a marked load",
269 …ad either shared or modified data from another core's L2/L3 on the same chip due to a marked load",
275 …rom another chip's L2 or L3 on the same Node or Group (Remote), as this chip due to a marked load",
281 …rom another chip's L2 or L3 on the same Node or Group (Remote), as this chip due to a marked load",
287 …rom another chip's L2 or L3 on the same Node or Group (Remote), as this chip due to a marked load",
293 …rom another chip's L2 or L3 on the same Node or Group (Remote), as this chip due to a marked load",
299 …ache was reloaded from another chip's L4 on the same Node or Group ( Remote) due to a marked load",
305 … cycles to reload from another chip's L4 on the same Node or Group ( Remote) due to a marked load",
311 … was reloaded from another chip's memory on the same Node or Group ( Remote) due to a marked load",
317 …les to reload from another chip's memory on the same Node or Group ( Remote) due to a marked load",
365 …other chip's L2 or L3 on a different Node or Group (Distant), as this chip due to a marked data si…
371 …other chip's L2 or L3 on a different Node or Group (Distant), as this chip due to a marked data si…
377 …into the TLB from another chip's L4 on a different Node or Group (Distant) due to a marked data si…
383 …nto the TLB from another chip's memory on the same Node or Group (Distant) due to a marked data si…
389 …"BriefDescription": "A Page Table Entry was loaded into the TLB from local core's L2 due to a mark…
395 …try was loaded into the TLB from a location other than the local core's L2 due to a marked data si…
401 …the TLB from local core's L2 hit without dispatch conflicts on Mepf state. due to a marked data si…
407 … Table Entry was loaded into the TLB from local core's L2 without conflict due to a marked data si…
413 …"BriefDescription": "A Page Table Entry was loaded into the TLB from local core's L3 due to a mark…
419 …try was loaded into the TLB from a location other than the local core's L3 due to a marked data si…
425 … Entry was loaded into the TLB from local core's L3 with dispatch conflict due to a marked data si…
431 …the TLB from local core's L3 without dispatch conflicts hit on Mepf state. due to a marked data si…
437 … Table Entry was loaded into the TLB from local core's L3 without conflict due to a marked data si…
443 …"A Page Table Entry was loaded into the TLB from the local chip's L4 cache due to a marked data si…
449 …: "A Page Table Entry was loaded into the TLB from the local chip's Memory due to a marked data si…
455 …o the TLB from a memory location including L4 from local remote or distant due to a marked data si…
461 …ied data from another core's L2/L3 on a different chip (remote or distant) due to a marked data si…
467 … either shared or modified data from another core's L2/L3 on the same chip due to a marked data si…
473 …m another chip's L2 or L3 on the same Node or Group (Remote), as this chip due to a marked data si…
479 …m another chip's L2 or L3 on the same Node or Group (Remote), as this chip due to a marked data si…
485 …ed into the TLB from another chip's L4 on the same Node or Group ( Remote) due to a marked data si…
491 …nto the TLB from another chip's memory on the same Node or Group ( Remote) due to a marked data si…