x86/goldmont/pipeline.json

164 …e core frequency may change from time to time. For this reason this event may have a changing rati…
189 …nge from time.  This event is not affected by core frequency changes but counts as if the core is …
224 …S records can be collected only on IA32_PMC0, only one event can use the PEBS facility at a time.",
228         "BriefDescription": "Unfilled issue slots per cycle",
232 …"PublicDescription": "Counts the number of issue slots per core cycle that were not consumed by th…
236         "BriefDescription": "Unfilled issue slots per cycle to recover",
240 …slots per core cycle that were not consumed by the backend because allocation is stalled waiting f…
245 …    "BriefDescription": "Unfilled issue slots per cycle because of a full resource in the backend",
249 …ssue slots per core cycle that were not consumed because of a full resource in the backend.  Inclu…
279 …, but did not occur because the store data was not available at the right time.  The forward might…
316 …ious unretired store in the pipeline whose address was not known at issue time, but is later resol…
321         "BriefDescription": "Self-Modifying Code detected",
325 …ction and has to perform a machine clear because of that modification.  Self-modifying code (SMC) …
334 …ed includes, but is not limited to those uops issued in the shadow of a miss-predicted branch, tho…
338         "BriefDescription": "Uops requested but not-delivered to the back-end per cycle",
342 …-end inefficiencies. I.e. when front-end of the machine is not delivering uops to the back-end and…
370 …ued by the micro-sequencer (MS).  Counts both the uops from a micro-coded instruction, and the uop…