1[
2    {
3        "BriefDescription": "read requests to memory controller. Derived from unc_m_cas_count.rd",
4        "Counter": "0,1,2,3",
5        "EventCode": "0x4",
6        "EventName": "LLC_MISSES.MEM_READ",
7        "PerPkg": "1",
8        "ScaleUnit": "64Bytes",
9        "UMask": "0x3",
10        "Unit": "iMC"
11    },
12    {
13        "BriefDescription": "write requests to memory controller. Derived from unc_m_cas_count.wr",
14        "Counter": "0,1,2,3",
15        "EventCode": "0x4",
16        "EventName": "LLC_MISSES.MEM_WRITE",
17        "PerPkg": "1",
18        "ScaleUnit": "64Bytes",
19        "UMask": "0xC",
20        "Unit": "iMC"
21    },
22    {
23        "BriefDescription": "Memory controller clock ticks",
24        "Counter": "0,1,2,3",
25        "EventName": "UNC_M_CLOCKTICKS",
26        "PerPkg": "1",
27        "Unit": "iMC"
28    },
29    {
30        "BriefDescription": "Cycles where DRAM ranks are in power down (CKE) mode+C37",
31        "Counter": "0,1,2,3",
32        "EventCode": "0x85",
33        "EventName": "UNC_M_POWER_CHANNEL_PPD",
34        "MetricExpr": "(UNC_M_POWER_CHANNEL_PPD / UNC_M_CLOCKTICKS) * 100.",
35        "MetricName": "power_channel_ppd %",
36        "PerPkg": "1",
37        "Unit": "iMC"
38    },
39    {
40        "BriefDescription": "Cycles Memory is in self refresh power mode",
41        "Counter": "0,1,2,3",
42        "EventCode": "0x43",
43        "EventName": "UNC_M_POWER_SELF_REFRESH",
44        "MetricExpr": "(UNC_M_POWER_SELF_REFRESH / UNC_M_CLOCKTICKS) * 100.",
45        "MetricName": "power_self_refresh %",
46        "PerPkg": "1",
47        "Unit": "iMC"
48    },
49    {
50        "BriefDescription": "Pre-charges due to page misses",
51        "Counter": "0,1,2,3",
52        "EventCode": "0x2",
53        "EventName": "UNC_M_PRE_COUNT.PAGE_MISS",
54        "PerPkg": "1",
55        "UMask": "0x1",
56        "Unit": "iMC"
57    },
58    {
59        "BriefDescription": "Pre-charge for reads",
60        "Counter": "0,1,2,3",
61        "EventCode": "0x2",
62        "EventName": "UNC_M_PRE_COUNT.RD",
63        "PerPkg": "1",
64        "UMask": "0x4",
65        "Unit": "iMC"
66    },
67    {
68        "BriefDescription": "Pre-charge for writes",
69        "Counter": "0,1,2,3",
70        "EventCode": "0x2",
71        "EventName": "UNC_M_PRE_COUNT.WR",
72        "PerPkg": "1",
73        "UMask": "0x8",
74        "Unit": "iMC"
75    },
76    {
77        "BriefDescription": "Write requests allocated in the PMM Write Pending Queue for Intel Optane DC persistent memory",
78        "Counter": "0,1,2,3",
79        "EventCode": "0xE3",
80        "EventName": "UNC_M_PMM_RPQ_INSERTS",
81        "PerPkg": "1",
82        "Unit": "iMC"
83    },
84    {
85        "BriefDescription": "Write requests allocated in the PMM Write Pending Queue for Intel Optane DC persistent memory",
86        "Counter": "0,1,2,3",
87        "EventCode": "0xE7",
88        "EventName": "UNC_M_PMM_WPQ_INSERTS",
89        "PerPkg": "1",
90        "Unit": "iMC"
91    },
92    {
93        "BriefDescription": "Intel Optane DC persistent memory bandwidth read (MB). Derived from unc_m_pmm_rpq_inserts",
94        "Counter": "0,1,2,3",
95        "EventCode": "0xE3",
96        "EventName": "UNC_M_PMM_BANDWIDTH.READ",
97        "PerPkg": "1",
98        "ScaleUnit": "6.103515625E-5MB",
99        "Unit": "iMC"
100    },
101    {
102        "BriefDescription": "Intel Optane DC persistent memory bandwidth write (MB). Derived from unc_m_pmm_wpq_inserts",
103        "Counter": "0,1,2,3",
104        "EventCode": "0xE7",
105        "EventName": "UNC_M_PMM_BANDWIDTH.WRITE",
106        "PerPkg": "1",
107        "ScaleUnit": "6.103515625E-5MB",
108        "Unit": "iMC"
109    },
110    {
111        "BriefDescription": "Intel Optane DC persistent memory bandwidth total (MB). Derived from unc_m_pmm_rpq_inserts",
112        "Counter": "0,1,2,3",
113        "EventCode": "0xE3",
114        "EventName": "UNC_M_PMM_BANDWIDTH.TOTAL",
115        "MetricExpr": "UNC_M_PMM_RPQ_INSERTS + UNC_M_PMM_WPQ_INSERTS",
116        "MetricName": "UNC_M_PMM_BANDWIDTH.TOTAL",
117        "PerPkg": "1",
118        "ScaleUnit": "6.103515625E-5MB",
119        "Unit": "iMC"
120    },
121    {
122        "BriefDescription": "Read Pending Queue Occupancy of all read requests for Intel Optane DC persistent memory",
123        "Counter": "0,1,2,3",
124        "EventCode": "0xE0",
125        "EventName": "UNC_M_PMM_RPQ_OCCUPANCY.ALL",
126        "PerPkg": "1",
127        "UMask": "0x1",
128        "Unit": "iMC"
129    },
130    {
131        "BriefDescription": "Intel Optane DC persistent memory read latency (ns). Derived from unc_m_pmm_rpq_occupancy.all",
132        "Counter": "0,1,2,3",
133        "EventCode": "0xE0",
134        "EventName": "UNC_M_PMM_READ_LATENCY",
135        "MetricExpr": "UNC_M_PMM_RPQ_OCCUPANCY.ALL / UNC_M_PMM_RPQ_INSERTS / UNC_M_CLOCKTICKS",
136        "MetricName": "UNC_M_PMM_READ_LATENCY",
137        "PerPkg": "1",
138        "ScaleUnit": "6000000000ns",
139        "UMask": "0x1",
140        "Unit": "iMC"
141    },
142    {
143        "BriefDescription": "DRAM Page Activate commands sent due to a write request",
144        "Counter": "0,1,2,3",
145        "EventCode": "0x1",
146        "EventName": "UNC_M_ACT_COUNT.WR",
147        "PerPkg": "1",
148        "PublicDescription": "Counts DRAM Page Activate commands sent on this channel due to a write request to the iMC (Memory Controller).  Activate commands are issued to open up a page on the DRAM devices so that it can be read or written to with a CAS (Column Access Select) command.",
149        "UMask": "0x2",
150        "Unit": "iMC"
151    },
152    {
153        "BriefDescription": "All DRAM CAS Commands issued",
154        "Counter": "0,1,2,3",
155        "EventCode": "0x4",
156        "EventName": "UNC_M_CAS_COUNT.ALL",
157        "PerPkg": "1",
158        "PublicDescription": "Counts all CAS (Column Address Select) commands issued to DRAM per memory channel.  CAS commands are issued to specify the address to read or write on DRAM, so this event increments for every read and write. This event counts whether AutoPrecharge (which closes the DRAM Page automatically after a read/write) is enabled or not.",
159        "UMask": "0xF",
160        "Unit": "iMC"
161    },
162    {
163        "BriefDescription": "All DRAM Read CAS Commands issued (does not include underfills)",
164        "Counter": "0,1,2,3",
165        "EventCode": "0x4",
166        "EventName": "UNC_M_CAS_COUNT.RD_REG",
167        "PerPkg": "1",
168        "PublicDescription": "Counts CAS (Column Access Select) regular read commands issued to DRAM on a per channel basis.  CAS commands are issued to specify the address to read or write on DRAM, and this event increments for every regular read.  This event only counts regular reads and does not includes underfill reads due to partial write requests.  This event counts whether AutoPrecharge (which closes the DRAM Page automatically after a read/write)  is enabled or not.",
169        "UMask": "0x1",
170        "Unit": "iMC"
171    },
172    {
173        "BriefDescription": "DRAM Underfill Read CAS Commands issued",
174        "Counter": "0,1,2,3",
175        "EventCode": "0x4",
176        "EventName": "UNC_M_CAS_COUNT.RD_UNDERFILL",
177        "PerPkg": "1",
178        "PublicDescription": "Counts CAS (Column Access Select) underfill read commands issued to DRAM due to a partial write, on a per channel basis.  CAS commands are issued to specify the address to read or write on DRAM, and this command counts underfill reads.  Partial writes must be completed by first reading in the underfill from DRAM and then merging in the partial write data before writing the full line back to DRAM. This event will generally count about the same as the number of partial writes, but may be slightly less because of partials hitting in the WPQ (due to a previous write request).",
179        "UMask": "0x2",
180        "Unit": "iMC"
181    },
182    {
183        "BriefDescription": "DRAM CAS (Column Address Strobe) Commands.; DRAM WR_CAS (w/ and w/out auto-pre) in Write Major Mode",
184        "Counter": "0,1,2,3",
185        "EventCode": "0x4",
186        "EventName": "UNC_M_CAS_COUNT.WR_WMM",
187        "PerPkg": "1",
188        "PublicDescription": "Counts the total number or DRAM Write CAS commands issued on this channel while in Write-Major-Mode.",
189        "UMask": "0x4",
190        "Unit": "iMC"
191    },
192    {
193        "BriefDescription": "All commands for Intel Optane DC persistent memory",
194        "Counter": "0,1,2,3",
195        "EventCode": "0xEA",
196        "EventName": "UNC_M_PMM_CMD1.ALL",
197        "PerPkg": "1",
198        "PublicDescription": "All commands for Intel Optane DC persistent memory",
199        "UMask": "0x1",
200        "Unit": "iMC"
201    },
202    {
203        "BriefDescription": "Regular reads(RPQ) commands for Intel Optane DC persistent memory",
204        "Counter": "0,1,2,3",
205        "EventCode": "0xEA",
206        "EventName": "UNC_M_PMM_CMD1.RD",
207        "PerPkg": "1",
208        "PublicDescription": "All Reads - RPQ or Ufill",
209        "UMask": "0x2",
210        "Unit": "iMC"
211    },
212    {
213        "BriefDescription": "Underfill read commands for Intel Optane DC persistent memory",
214        "Counter": "0,1,2,3",
215        "EventCode": "0xEA",
216        "EventName": "UNC_M_PMM_CMD1.UFILL_RD",
217        "PerPkg": "1",
218        "PublicDescription": "Underfill reads",
219        "UMask": "0x8",
220        "Unit": "iMC"
221    },
222    {
223        "BriefDescription": "Write commands for Intel Optane DC persistent memory",
224        "Counter": "0,1,2,3",
225        "EventCode": "0xEA",
226        "EventName": "UNC_M_PMM_CMD1.WR",
227        "PerPkg": "1",
228        "PublicDescription": "Writes",
229        "UMask": "0x4",
230        "Unit": "iMC"
231    },
232    {
233        "BriefDescription": "Write Pending Queue Occupancy of all write requests for Intel Optane DC persistent memory",
234        "Counter": "0,1,2,3",
235        "EventCode": "0xE4",
236        "EventName": "UNC_M_PMM_WPQ_OCCUPANCY.ALL",
237        "PerPkg": "1",
238        "PublicDescription": "Write Pending Queue Occupancy of all write requests for Intel Optane DC persistent memory",
239        "UMask": "0x1",
240        "Unit": "iMC"
241    },
242    {
243        "BriefDescription": "Read Pending Queue Allocations",
244        "Counter": "0,1,2,3",
245        "EventCode": "0x10",
246        "EventName": "UNC_M_RPQ_INSERTS",
247        "PerPkg": "1",
248        "PublicDescription": "Counts the number of read requests allocated into the Read Pending Queue (RPQ).  This queue is used to schedule reads out to the memory controller and to track the requests.  Requests allocate into the RPQ soon after they enter the memory controller, and need credits for an entry in this buffer before being sent from the CHA to the iMC.  The requests deallocate after the read CAS command has been issued to DRAM.  This event counts both Isochronous and non-Isochronous requests which were issued to the RPQ.",
249        "Unit": "iMC"
250    },
251    {
252        "BriefDescription": "Read Pending Queue Occupancy",
253        "Counter": "0,1,2,3",
254        "EventCode": "0x80",
255        "EventName": "UNC_M_RPQ_OCCUPANCY",
256        "PerPkg": "1",
257        "PublicDescription": "Counts the number of entries in the Read Pending Queue (RPQ) at each cycle.  This can then be used to calculate both the average occupancy of the queue (in conjunction with the number of cycles not empty) and the average latency in the queue (in conjunction with the number of allocations).  The RPQ is used to schedule reads out to the memory controller and to track the requests.  Requests allocate into the RPQ soon after they enter the memory controller, and need credits for an entry in this buffer before being sent from the CHA to the iMC. They deallocate from the RPQ after the CAS command has been issued to memory.",
258        "Unit": "iMC"
259    },
260    {
261        "BriefDescription": "All hits to Near Memory(DRAM cache) in Memory Mode",
262        "Counter": "0,1,2,3",
263        "EventCode": "0xD3",
264        "EventName": "UNC_M_TAGCHK.HIT",
265        "PerPkg": "1",
266        "PublicDescription": "Tag Check; Hit",
267        "UMask": "0x1",
268        "Unit": "iMC"
269    },
270    {
271        "BriefDescription": "All Clean line misses to Near Memory(DRAM cache) in Memory Mode",
272        "Counter": "0,1,2,3",
273        "EventCode": "0xD3",
274        "EventName": "UNC_M_TAGCHK.MISS_CLEAN",
275        "PerPkg": "1",
276        "PublicDescription": "Tag Check; Clean",
277        "UMask": "0x2",
278        "Unit": "iMC"
279    },
280    {
281        "BriefDescription": "All dirty line misses to Near Memory(DRAM cache) in Memory Mode",
282        "Counter": "0,1,2,3",
283        "EventCode": "0xD3",
284        "EventName": "UNC_M_TAGCHK.MISS_DIRTY",
285        "PerPkg": "1",
286        "PublicDescription": "Tag Check; Dirty",
287        "UMask": "0x4",
288        "Unit": "iMC"
289    },
290    {
291        "BriefDescription": "Write Pending Queue Allocations",
292        "Counter": "0,1,2,3",
293        "EventCode": "0x20",
294        "EventName": "UNC_M_WPQ_INSERTS",
295        "PerPkg": "1",
296        "PublicDescription": "Counts the number of writes requests allocated into the Write Pending Queue (WPQ).  The WPQ is used to schedule writes out to the memory controller and to track the requests.  Requests allocate into the WPQ soon after they enter the memory controller, and need credits for an entry in this buffer before being sent from the CHA to the iMC (Memory Controller).  The write requests deallocate after being issued to DRAM.  Write requests themselves are able to complete (from the perspective of the rest of the system) as soon they have 'posted' to the iMC.",
297        "Unit": "iMC"
298    },
299    {
300        "BriefDescription": "Write Pending Queue Occupancy",
301        "Counter": "0,1,2,3",
302        "EventCode": "0x81",
303        "EventName": "UNC_M_WPQ_OCCUPANCY",
304        "PerPkg": "1",
305        "PublicDescription": "Counts the number of entries in the Write Pending Queue (WPQ) at each cycle.  This can then be used to calculate both the average queue occupancy (in conjunction with the number of cycles not empty) and the average latency (in conjunction with the number of allocations).  The WPQ is used to schedule writes out to the memory controller and to track the requests.  Requests allocate into the WPQ soon after they enter the memory controller, and need credits for an entry in this buffer before being sent from the CHA to the iMC (memory controller).  They deallocate after being issued to DRAM.  Write requests themselves are able to complete (from the perspective of the rest of the system) as soon they have 'posted' to the iMC.  This is not to be confused with actually performing the write to DRAM.  Therefore, the average latency for this queue is actually not useful for deconstruction intermediate write latencies.  So, we provide filtering based on if the request has posted or not.  By using the 'not posted' filter, we can track how long writes spent in the iMC before completions were sent to the HA.  The 'posted' filter, on the other hand, provides information about how much queueing is actually happenning in the iMC for writes before they are actually issued to memory.  High average occupancies will generally coincide with high write major mode counts. Is there a filter of sorts???",
306        "Unit": "iMC"
307    }
308]
309