|
1 | 1 | [ |
2 | 2 | { |
3 | 3 | "BriefDescription": "Counts the number of baclears", |
4 | | - "Counter": "0,1", |
5 | 4 | "EventCode": "0xE6", |
6 | 5 | "EventName": "BACLEARS.ALL", |
7 | 6 | "PublicDescription": "The BACLEARS event counts the number of times the front end is resteered, mainly when the Branch Prediction Unit cannot provide a correct prediction and this is corrected by the Branch Address Calculator at the front end. The BACLEARS.ANY event counts the number of baclears for any type of branch.", |
|
10 | 9 | }, |
11 | 10 | { |
12 | 11 | "BriefDescription": "Counts the number of JCC baclears", |
13 | | - "Counter": "0,1", |
14 | 12 | "EventCode": "0xE6", |
15 | 13 | "EventName": "BACLEARS.COND", |
16 | 14 | "PublicDescription": "The BACLEARS event counts the number of times the front end is resteered, mainly when the Branch Prediction Unit cannot provide a correct prediction and this is corrected by the Branch Address Calculator at the front end. The BACLEARS.COND event counts the number of JCC (Jump on Condtional Code) baclears.", |
|
19 | 17 | }, |
20 | 18 | { |
21 | 19 | "BriefDescription": "Counts the number of RETURN baclears", |
22 | | - "Counter": "0,1", |
23 | 20 | "EventCode": "0xE6", |
24 | 21 | "EventName": "BACLEARS.RETURN", |
25 | 22 | "PublicDescription": "The BACLEARS event counts the number of times the front end is resteered, mainly when the Branch Prediction Unit cannot provide a correct prediction and this is corrected by the Branch Address Calculator at the front end. The BACLEARS.RETURN event counts the number of RETURN baclears.", |
|
28 | 25 | }, |
29 | 26 | { |
30 | 27 | "BriefDescription": "Counts the number of times a decode restriction reduced the decode throughput due to wrong instruction length prediction", |
31 | | - "Counter": "0,1", |
32 | 28 | "EventCode": "0xE9", |
33 | 29 | "EventName": "DECODE_RESTRICTION.PREDECODE_WRONG", |
34 | 30 | "PublicDescription": "Counts the number of times a decode restriction reduced the decode throughput due to wrong instruction length prediction.", |
|
37 | 33 | }, |
38 | 34 | { |
39 | 35 | "BriefDescription": "Instruction fetches", |
40 | | - "Counter": "0,1", |
41 | 36 | "EventCode": "0x80", |
42 | 37 | "EventName": "ICACHE.ACCESSES", |
43 | 38 | "PublicDescription": "This event counts all instruction fetches, not including most uncacheable\r\nfetches.", |
|
46 | 41 | }, |
47 | 42 | { |
48 | 43 | "BriefDescription": "Instruction fetches from Icache", |
49 | | - "Counter": "0,1", |
50 | 44 | "EventCode": "0x80", |
51 | 45 | "EventName": "ICACHE.HIT", |
52 | 46 | "PublicDescription": "This event counts all instruction fetches from the instruction cache.", |
|
55 | 49 | }, |
56 | 50 | { |
57 | 51 | "BriefDescription": "Icache miss", |
58 | | - "Counter": "0,1", |
59 | 52 | "EventCode": "0x80", |
60 | 53 | "EventName": "ICACHE.MISSES", |
61 | 54 | "PublicDescription": "This event counts all instruction fetches that miss the Instruction cache or produce memory requests. This includes uncacheable fetches. An instruction fetch miss is counted only once and not once for every cycle it is outstanding.", |
|
64 | 57 | }, |
65 | 58 | { |
66 | 59 | "BriefDescription": "Counts the number of times entered into a ucode flow in the FEC. Includes inserted flows due to front-end detected faults or assists. Speculative count.", |
67 | | - "Counter": "0,1", |
68 | 60 | "EventCode": "0xE7", |
69 | 61 | "EventName": "MS_DECODED.MS_ENTRY", |
70 | 62 | "PublicDescription": "Counts the number of times the MSROM starts a flow of UOPS. It does not count every time a UOP is read from the microcode ROM. The most common case that this counts is when a micro-coded instruction is encountered by the front end of the machine. Other cases include when an instruction encounters a fault, trap, or microcode assist of any sort. The event will count MSROM startups for UOPS that are speculative, and subsequently cleared by branch mispredict or machine clear. Background: UOPS are produced by two mechanisms. Either they are generated by hardware that decodes instructions into UOPS, or they are delivered by a ROM (called the MSROM) that holds UOPS associated with a specific instruction. MSROM UOPS might also be delivered in response to some condition such as a fault or other exceptional condition. This event is an excellent mechanism for detecting instructions that require the use of MSROM instructions.", |
|
0 commit comments