-
Notifications
You must be signed in to change notification settings - Fork 345
/
Copy pathjkt_uc.py
5178 lines (5162 loc) · 343 KB
/
jkt_uc.py
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
# Support for Intel Xeon E5 2600 series uncore monitoring
# see http://www.intel.com/content/dam/www/public/us/en/documents/design-guides/xeon-e5-2600-uncore-guide.pdf
# for more details on the events and formulas.
# aliases
aliases = {
"QPIMatch1": "Q_Py_PCI_PMON_PKT_MATCH1",
"QPIMask0": "Q_Py_PCI_PMON_PKT_MASK0",
"QPIMatch0": "Q_Py_PCI_PMON_BOX_MATCH0",
"PCUFilter": "PCU_MSR_PMON_BOX_FILTER",
"CBoFilter": "Cn_MSR_PMON_BOX_FILTER",
"QPIMask1": "Q_Py_PCI_PMON_PKT_MASK1",
}
events = {
# R3QPI:
"R3QPI.CLOCKTICKS": {
"Box": "R3QPI",
"Category": "R3QPI UCLK Events",
"Counters": "0-2",
"Defn": "Counts the number of uclks in the QPI uclk domain. This could be slightly different than the count in the Ubox because of enable/freeze delays. However, because the QPI Agent is close to the Ubox, they generally should not diverge by more than a handful of cycles.",
"Desc": "Number of uclks in domain",
"EvSel": 1,
},
"R3QPI.IIO_CREDITS_ACQUIRED": {
"Box": "R3QPI",
"Category": "R3QPI IIO_CREDITS Events",
"Counters": "0-1",
"Defn": "Counts the number of times the NCS/NCB/DRS credit is acquired in the QPI for sending messages on BL to the IIO. There is one credit for each of these three message classes (three credits total). NCS is used for reads to PCIe space, NCB is used for transfering data without coherency, and DRS is used for transfering data with coherency (cachable PCI transactions). This event can only track one message class at a time.",
"Desc": "to IIO BL Credit Acquired",
"EvSel": 32,
},
"R3QPI.IIO_CREDITS_ACQUIRED.NCS": {
"Box": "R3QPI",
"Category": "R3QPI IIO_CREDITS Events",
"Counters": "0-1",
"Defn": "Counts the number of times the NCS/NCB/DRS credit is acquired in the QPI for sending messages on BL to the IIO. There is one credit for each of these three message classes (three credits total). NCS is used for reads to PCIe space, NCB is used for transfering data without coherency, and DRS is used for transfering data with coherency (cachable PCI transactions). This event can only track one message class at a time.",
"Desc": "to IIO BL Credit Acquired",
"EvSel": 32,
"Umask": "bxx1xxxxx",
},
"R3QPI.IIO_CREDITS_ACQUIRED.NCB": {
"Box": "R3QPI",
"Category": "R3QPI IIO_CREDITS Events",
"Counters": "0-1",
"Defn": "Counts the number of times the NCS/NCB/DRS credit is acquired in the QPI for sending messages on BL to the IIO. There is one credit for each of these three message classes (three credits total). NCS is used for reads to PCIe space, NCB is used for transfering data without coherency, and DRS is used for transfering data with coherency (cachable PCI transactions). This event can only track one message class at a time.",
"Desc": "to IIO BL Credit Acquired",
"EvSel": 32,
"Umask": "bxxx1xxxx",
},
"R3QPI.IIO_CREDITS_ACQUIRED.DRS": {
"Box": "R3QPI",
"Category": "R3QPI IIO_CREDITS Events",
"Counters": "0-1",
"Defn": "Counts the number of times the NCS/NCB/DRS credit is acquired in the QPI for sending messages on BL to the IIO. There is one credit for each of these three message classes (three credits total). NCS is used for reads to PCIe space, NCB is used for transfering data without coherency, and DRS is used for transfering data with coherency (cachable PCI transactions). This event can only track one message class at a time.",
"Desc": "to IIO BL Credit Acquired",
"EvSel": 32,
"Umask": "bxxxx1xxx",
},
"R3QPI.IIO_CREDITS_REJECT": {
"Box": "R3QPI",
"Category": "R3QPI IIO_CREDITS Events",
"Counters": "0-1",
"Defn": "Counts the number of times that a request attempted to acquire an NCS/NCB/DRS credit in the QPI for sending messages on BL to the IIO but was rejected because no credit was available. There is one credit for each of these three message classes (three credits total). NCS is used for reads to PCIe space, NCB is used for transfering data without coherency, and DRS is used for transfering data with coherency (cachable PCI transactions). This event can only track one message class at a time.",
"Desc": "to IIO BL Credit Rejected",
"EvSel": 33,
},
"R3QPI.IIO_CREDITS_REJECT.NCS": {
"Box": "R3QPI",
"Category": "R3QPI IIO_CREDITS Events",
"Counters": "0-1",
"Defn": "Counts the number of times that a request attempted to acquire an NCS/NCB/DRS credit in the QPI for sending messages on BL to the IIO but was rejected because no credit was available. There is one credit for each of these three message classes (three credits total). NCS is used for reads to PCIe space, NCB is used for transfering data without coherency, and DRS is used for transfering data with coherency (cachable PCI transactions). This event can only track one message class at a time.",
"Desc": "to IIO BL Credit Rejected",
"EvSel": 33,
"Umask": "bxx1xxxxx",
},
"R3QPI.IIO_CREDITS_REJECT.NCB": {
"Box": "R3QPI",
"Category": "R3QPI IIO_CREDITS Events",
"Counters": "0-1",
"Defn": "Counts the number of times that a request attempted to acquire an NCS/NCB/DRS credit in the QPI for sending messages on BL to the IIO but was rejected because no credit was available. There is one credit for each of these three message classes (three credits total). NCS is used for reads to PCIe space, NCB is used for transfering data without coherency, and DRS is used for transfering data with coherency (cachable PCI transactions). This event can only track one message class at a time.",
"Desc": "to IIO BL Credit Rejected",
"EvSel": 33,
"Umask": "bxxx1xxxx",
},
"R3QPI.IIO_CREDITS_REJECT.DRS": {
"Box": "R3QPI",
"Category": "R3QPI IIO_CREDITS Events",
"Counters": "0-1",
"Defn": "Counts the number of times that a request attempted to acquire an NCS/NCB/DRS credit in the QPI for sending messages on BL to the IIO but was rejected because no credit was available. There is one credit for each of these three message classes (three credits total). NCS is used for reads to PCIe space, NCB is used for transfering data without coherency, and DRS is used for transfering data with coherency (cachable PCI transactions). This event can only track one message class at a time.",
"Desc": "to IIO BL Credit Rejected",
"EvSel": 33,
"Umask": "bxxxx1xxx",
},
"R3QPI.IIO_CREDITS_USED": {
"Box": "R3QPI",
"Category": "R3QPI IIO_CREDITS Events",
"Counters": "0-1",
"Defn": "Counts the number of cycles when the NCS/NCB/DRS credit is in use in the QPI for sending messages on BL to the IIO. There is one credit for each of these three message classes (three credits total). NCS is used for reads to PCIe space, NCB is used for transfering data without coherency, and DRS is used for transfering data with coherency (cachable PCI transactions). This event can only track one message class at a time.",
"Desc": "to IIO BL Credit In Use",
"EvSel": 34,
},
"R3QPI.IIO_CREDITS_USED.NCS": {
"Box": "R3QPI",
"Category": "R3QPI IIO_CREDITS Events",
"Counters": "0-1",
"Defn": "Counts the number of cycles when the NCS/NCB/DRS credit is in use in the QPI for sending messages on BL to the IIO. There is one credit for each of these three message classes (three credits total). NCS is used for reads to PCIe space, NCB is used for transfering data without coherency, and DRS is used for transfering data with coherency (cachable PCI transactions). This event can only track one message class at a time.",
"Desc": "to IIO BL Credit In Use",
"EvSel": 34,
"Umask": "bxx1xxxxx",
},
"R3QPI.IIO_CREDITS_USED.NCB": {
"Box": "R3QPI",
"Category": "R3QPI IIO_CREDITS Events",
"Counters": "0-1",
"Defn": "Counts the number of cycles when the NCS/NCB/DRS credit is in use in the QPI for sending messages on BL to the IIO. There is one credit for each of these three message classes (three credits total). NCS is used for reads to PCIe space, NCB is used for transfering data without coherency, and DRS is used for transfering data with coherency (cachable PCI transactions). This event can only track one message class at a time.",
"Desc": "to IIO BL Credit In Use",
"EvSel": 34,
"Umask": "bxxx1xxxx",
},
"R3QPI.IIO_CREDITS_USED.DRS": {
"Box": "R3QPI",
"Category": "R3QPI IIO_CREDITS Events",
"Counters": "0-1",
"Defn": "Counts the number of cycles when the NCS/NCB/DRS credit is in use in the QPI for sending messages on BL to the IIO. There is one credit for each of these three message classes (three credits total). NCS is used for reads to PCIe space, NCB is used for transfering data without coherency, and DRS is used for transfering data with coherency (cachable PCI transactions). This event can only track one message class at a time.",
"Desc": "to IIO BL Credit In Use",
"EvSel": 34,
"Umask": "bxxxx1xxx",
},
"R3QPI.RING_AD_USED": {
"Box": "R3QPI",
"Category": "R3QPI RING Events",
"Counters": "0-2",
"Defn": "Counts the number of cycles that the AD ring is being used at this ring stop. This includes when packets are passing by and when packets are being sunk, but does not include when packets are being sent from the ring stop.",
"Desc": "R3 AD Ring in Use",
"EvSel": 7,
},
"R3QPI.RING_AD_USED.CW_EVEN": {
"Box": "R3QPI",
"Category": "R3QPI RING Events",
"Counters": "0-2",
"Defn": "Counts the number of cycles that the AD ring is being used at this ring stop. This includes when packets are passing by and when packets are being sunk, but does not include when packets are being sent from the ring stop.",
"Desc": "R3 AD Ring in Use",
"EvSel": 7,
"Umask": "bxxxxxxx1",
},
"R3QPI.RING_AD_USED.CCW_EVEN": {
"Box": "R3QPI",
"Category": "R3QPI RING Events",
"Counters": "0-2",
"Defn": "Counts the number of cycles that the AD ring is being used at this ring stop. This includes when packets are passing by and when packets are being sunk, but does not include when packets are being sent from the ring stop.",
"Desc": "R3 AD Ring in Use",
"EvSel": 7,
"Umask": "bxxxxx1xx",
},
"R3QPI.RING_AD_USED.CW_ODD": {
"Box": "R3QPI",
"Category": "R3QPI RING Events",
"Counters": "0-2",
"Defn": "Counts the number of cycles that the AD ring is being used at this ring stop. This includes when packets are passing by and when packets are being sunk, but does not include when packets are being sent from the ring stop.",
"Desc": "R3 AD Ring in Use",
"EvSel": 7,
"Umask": "bxxxxxx1x",
},
"R3QPI.RING_AD_USED.CCW_ODD": {
"Box": "R3QPI",
"Category": "R3QPI RING Events",
"Counters": "0-2",
"Defn": "Counts the number of cycles that the AD ring is being used at this ring stop. This includes when packets are passing by and when packets are being sunk, but does not include when packets are being sent from the ring stop.",
"Desc": "R3 AD Ring in Use",
"EvSel": 7,
"Umask": "bxxxx1xxx",
},
"R3QPI.RING_AK_USED": {
"Box": "R3QPI",
"Category": "R3QPI RING Events",
"Counters": "0-2",
"Defn": "Counts the number of cycles that the AK ring is being used at this ring stop. This includes when packets are passing by and when packets are being sent, but does not include when packets are being sunk into the ring stop.",
"Desc": "R3 AK Ring in Use",
"EvSel": 8,
},
"R3QPI.RING_AK_USED.CW_EVEN": {
"Box": "R3QPI",
"Category": "R3QPI RING Events",
"Counters": "0-2",
"Defn": "Counts the number of cycles that the AK ring is being used at this ring stop. This includes when packets are passing by and when packets are being sent, but does not include when packets are being sunk into the ring stop.",
"Desc": "R3 AK Ring in Use",
"EvSel": 8,
"Umask": "bxxxxxxx1",
},
"R3QPI.RING_AK_USED.CCW_EVEN": {
"Box": "R3QPI",
"Category": "R3QPI RING Events",
"Counters": "0-2",
"Defn": "Counts the number of cycles that the AK ring is being used at this ring stop. This includes when packets are passing by and when packets are being sent, but does not include when packets are being sunk into the ring stop.",
"Desc": "R3 AK Ring in Use",
"EvSel": 8,
"Umask": "bxxxxx1xx",
},
"R3QPI.RING_AK_USED.CW_ODD": {
"Box": "R3QPI",
"Category": "R3QPI RING Events",
"Counters": "0-2",
"Defn": "Counts the number of cycles that the AK ring is being used at this ring stop. This includes when packets are passing by and when packets are being sent, but does not include when packets are being sunk into the ring stop.",
"Desc": "R3 AK Ring in Use",
"EvSel": 8,
"Umask": "bxxxxxx1x",
},
"R3QPI.RING_AK_USED.CCW_ODD": {
"Box": "R3QPI",
"Category": "R3QPI RING Events",
"Counters": "0-2",
"Defn": "Counts the number of cycles that the AK ring is being used at this ring stop. This includes when packets are passing by and when packets are being sent, but does not include when packets are being sunk into the ring stop.",
"Desc": "R3 AK Ring in Use",
"EvSel": 8,
"Umask": "bxxxx1xxx",
},
"R3QPI.RING_BL_USED": {
"Box": "R3QPI",
"Category": "R3QPI RING Events",
"Counters": "0-2",
"Defn": "Counts the number of cycles that the BL ring is being used at this ring stop. This includes when packets are passing by and when packets are being sunk, but does not include when packets are being sent from the ring stop.",
"Desc": "R3 BL Ring in Use",
"EvSel": 9,
},
"R3QPI.RING_BL_USED.CW_EVEN": {
"Box": "R3QPI",
"Category": "R3QPI RING Events",
"Counters": "0-2",
"Defn": "Counts the number of cycles that the BL ring is being used at this ring stop. This includes when packets are passing by and when packets are being sunk, but does not include when packets are being sent from the ring stop.",
"Desc": "R3 BL Ring in Use",
"EvSel": 9,
"Umask": "bxxxxxxx1",
},
"R3QPI.RING_BL_USED.CCW_EVEN": {
"Box": "R3QPI",
"Category": "R3QPI RING Events",
"Counters": "0-2",
"Defn": "Counts the number of cycles that the BL ring is being used at this ring stop. This includes when packets are passing by and when packets are being sunk, but does not include when packets are being sent from the ring stop.",
"Desc": "R3 BL Ring in Use",
"EvSel": 9,
"Umask": "bxxxxx1xx",
},
"R3QPI.RING_BL_USED.CW_ODD": {
"Box": "R3QPI",
"Category": "R3QPI RING Events",
"Counters": "0-2",
"Defn": "Counts the number of cycles that the BL ring is being used at this ring stop. This includes when packets are passing by and when packets are being sunk, but does not include when packets are being sent from the ring stop.",
"Desc": "R3 BL Ring in Use",
"EvSel": 9,
"Umask": "bxxxxxx1x",
},
"R3QPI.RING_BL_USED.CCW_ODD": {
"Box": "R3QPI",
"Category": "R3QPI RING Events",
"Counters": "0-2",
"Defn": "Counts the number of cycles that the BL ring is being used at this ring stop. This includes when packets are passing by and when packets are being sunk, but does not include when packets are being sent from the ring stop.",
"Desc": "R3 BL Ring in Use",
"EvSel": 9,
"Umask": "bxxxx1xxx",
},
"R3QPI.RING_IV_USED": {
"Box": "R3QPI",
"Category": "R3QPI RING Events",
"Counters": "0-2",
"Defn": "Counts the number of cycles that the IV ring is being used at this ring stop. This includes when packets are passing by and when packets are being sent, but does not include when packets are being sunk into the ring stop. The IV ring is unidirectional. Whether UP or DN is used is dependent on the system programming. Thereofore, one should generally set both the UP and DN bits for a given polarity (or both) at a given time.",
"Desc": "R3 IV Ring in Use",
"EvSel": 10,
},
"R3QPI.RING_IV_USED.ANY": {
"Box": "R3QPI",
"Category": "R3QPI RING Events",
"Counters": "0-2",
"Defn": "Counts the number of cycles that the IV ring is being used at this ring stop. This includes when packets are passing by and when packets are being sent, but does not include when packets are being sunk into the ring stop. The IV ring is unidirectional. Whether UP or DN is used is dependent on the system programming. Thereofore, one should generally set both the UP and DN bits for a given polarity (or both) at a given time.",
"Desc": "R3 IV Ring in Use",
"EvSel": 10,
"Umask": "b00001111",
},
"R3QPI.RxR_BYPASSED": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": "0-1",
"Defn": "Counts the number of times when the Ingress was bypassed and an incoming transaction was bypassed directly across the BGF and into the qfclk domain.",
"Desc": "Ingress Bypassed",
"EvSel": 18,
},
"R3QPI.RxR_BYPASSED.AD": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": "0-1",
"Defn": "Counts the number of times when the Ingress was bypassed and an incoming transaction was bypassed directly across the BGF and into the qfclk domain.",
"Desc": "Ingress Bypassed",
"EvSel": 18,
"Umask": "bxxxxxxx1",
},
"R3QPI.RxR_CYCLES_NE": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": "0-1",
"Defn": "Counts the number of cycles when the QPI Ingress is not empty. This tracks one of the three rings that are used by the QPI agent. This can be used in conjunction with the QPI Ingress Occupancy Accumulator event in order to calculate average queue occupancy. Multiple ingress buffers can be tracked at a given time using multiple counters.",
"Desc": "Ingress Cycles Not Empty",
"EvSel": 16,
},
"R3QPI.RxR_CYCLES_NE.NCS": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": "0-1",
"Defn": "Counts the number of cycles when the QPI Ingress is not empty. This tracks one of the three rings that are used by the QPI agent. This can be used in conjunction with the QPI Ingress Occupancy Accumulator event in order to calculate average queue occupancy. Multiple ingress buffers can be tracked at a given time using multiple counters.",
"Desc": "Ingress Cycles Not Empty",
"EvSel": 16,
"Umask": "bxx1xxxxx",
},
"R3QPI.RxR_CYCLES_NE.NCB": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": "0-1",
"Defn": "Counts the number of cycles when the QPI Ingress is not empty. This tracks one of the three rings that are used by the QPI agent. This can be used in conjunction with the QPI Ingress Occupancy Accumulator event in order to calculate average queue occupancy. Multiple ingress buffers can be tracked at a given time using multiple counters.",
"Desc": "Ingress Cycles Not Empty",
"EvSel": 16,
"Umask": "bxxx1xxxx",
},
"R3QPI.RxR_CYCLES_NE.DRS": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": "0-1",
"Defn": "Counts the number of cycles when the QPI Ingress is not empty. This tracks one of the three rings that are used by the QPI agent. This can be used in conjunction with the QPI Ingress Occupancy Accumulator event in order to calculate average queue occupancy. Multiple ingress buffers can be tracked at a given time using multiple counters.",
"Desc": "Ingress Cycles Not Empty",
"EvSel": 16,
"Umask": "bxxxx1xxx",
},
"R3QPI.RxR_CYCLES_NE.SNP": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": "0-1",
"Defn": "Counts the number of cycles when the QPI Ingress is not empty. This tracks one of the three rings that are used by the QPI agent. This can be used in conjunction with the QPI Ingress Occupancy Accumulator event in order to calculate average queue occupancy. Multiple ingress buffers can be tracked at a given time using multiple counters.",
"Desc": "Ingress Cycles Not Empty",
"EvSel": 16,
"Umask": "bxxxxxx1x",
},
"R3QPI.RxR_CYCLES_NE.HOM": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": "0-1",
"Defn": "Counts the number of cycles when the QPI Ingress is not empty. This tracks one of the three rings that are used by the QPI agent. This can be used in conjunction with the QPI Ingress Occupancy Accumulator event in order to calculate average queue occupancy. Multiple ingress buffers can be tracked at a given time using multiple counters.",
"Desc": "Ingress Cycles Not Empty",
"EvSel": 16,
"Umask": "bxxxxxxx1",
},
"R3QPI.RxR_CYCLES_NE.NDR": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": "0-1",
"Defn": "Counts the number of cycles when the QPI Ingress is not empty. This tracks one of the three rings that are used by the QPI agent. This can be used in conjunction with the QPI Ingress Occupancy Accumulator event in order to calculate average queue occupancy. Multiple ingress buffers can be tracked at a given time using multiple counters.",
"Desc": "Ingress Cycles Not Empty",
"EvSel": 16,
"Umask": "bxxxxx1xx",
},
"R3QPI.RxR_INSERTS": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": "0-1",
"Defn": "Counts the number of allocations into the QPI Ingress. This tracks one of the three rings that are used by the QPI agent. This can be used in conjunction with the QPI Ingress Occupancy Accumulator event in order to calculate average queue latency. Multiple ingress buffers can be tracked at a given time using multiple counters.",
"Desc": "Ingress Allocations",
"EvSel": 17,
},
"R3QPI.RxR_INSERTS.NCS": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": "0-1",
"Defn": "Counts the number of allocations into the QPI Ingress. This tracks one of the three rings that are used by the QPI agent. This can be used in conjunction with the QPI Ingress Occupancy Accumulator event in order to calculate average queue latency. Multiple ingress buffers can be tracked at a given time using multiple counters.",
"Desc": "Ingress Allocations",
"EvSel": 17,
"Umask": "bxx1xxxxx",
},
"R3QPI.RxR_INSERTS.NCB": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": "0-1",
"Defn": "Counts the number of allocations into the QPI Ingress. This tracks one of the three rings that are used by the QPI agent. This can be used in conjunction with the QPI Ingress Occupancy Accumulator event in order to calculate average queue latency. Multiple ingress buffers can be tracked at a given time using multiple counters.",
"Desc": "Ingress Allocations",
"EvSel": 17,
"Umask": "bxxx1xxxx",
},
"R3QPI.RxR_INSERTS.DRS": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": "0-1",
"Defn": "Counts the number of allocations into the QPI Ingress. This tracks one of the three rings that are used by the QPI agent. This can be used in conjunction with the QPI Ingress Occupancy Accumulator event in order to calculate average queue latency. Multiple ingress buffers can be tracked at a given time using multiple counters.",
"Desc": "Ingress Allocations",
"EvSel": 17,
"Umask": "bxxxx1xxx",
},
"R3QPI.RxR_INSERTS.SNP": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": "0-1",
"Defn": "Counts the number of allocations into the QPI Ingress. This tracks one of the three rings that are used by the QPI agent. This can be used in conjunction with the QPI Ingress Occupancy Accumulator event in order to calculate average queue latency. Multiple ingress buffers can be tracked at a given time using multiple counters.",
"Desc": "Ingress Allocations",
"EvSel": 17,
"Umask": "bxxxxxx1x",
},
"R3QPI.RxR_INSERTS.HOM": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": "0-1",
"Defn": "Counts the number of allocations into the QPI Ingress. This tracks one of the three rings that are used by the QPI agent. This can be used in conjunction with the QPI Ingress Occupancy Accumulator event in order to calculate average queue latency. Multiple ingress buffers can be tracked at a given time using multiple counters.",
"Desc": "Ingress Allocations",
"EvSel": 17,
"Umask": "bxxxxxxx1",
},
"R3QPI.RxR_INSERTS.NDR": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": "0-1",
"Defn": "Counts the number of allocations into the QPI Ingress. This tracks one of the three rings that are used by the QPI agent. This can be used in conjunction with the QPI Ingress Occupancy Accumulator event in order to calculate average queue latency. Multiple ingress buffers can be tracked at a given time using multiple counters.",
"Desc": "Ingress Allocations",
"EvSel": 17,
"Umask": "bxxxxx1xx",
},
"R3QPI.RxR_OCCUPANCY": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": 0,
"Defn": "Accumulates the occupancy of a given QPI Ingress queue in each cycles. This tracks one of the three ring Ingress buffers. This can be used with the QPI Ingress Not Empty event to calculate average occupancy or the QPI Ingress Allocations event in order to calculate average queuing latency.",
"Desc": "Ingress Occupancy Accumulator",
"EvSel": 19,
"MaxIncCyc": 32,
"SubCtr": 1,
},
"R3QPI.RxR_OCCUPANCY.NCS": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": 0,
"Defn": "Accumulates the occupancy of a given QPI Ingress queue in each cycles. This tracks one of the three ring Ingress buffers. This can be used with the QPI Ingress Not Empty event to calculate average occupancy or the QPI Ingress Allocations event in order to calculate average queuing latency.",
"Desc": "Ingress Occupancy Accumulator",
"EvSel": 19,
"MaxIncCyc": 32,
"SubCtr": 1,
"Umask": "bxx1xxxxx",
},
"R3QPI.RxR_OCCUPANCY.NCB": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": 0,
"Defn": "Accumulates the occupancy of a given QPI Ingress queue in each cycles. This tracks one of the three ring Ingress buffers. This can be used with the QPI Ingress Not Empty event to calculate average occupancy or the QPI Ingress Allocations event in order to calculate average queuing latency.",
"Desc": "Ingress Occupancy Accumulator",
"EvSel": 19,
"MaxIncCyc": 32,
"SubCtr": 1,
"Umask": "bxxx1xxxx",
},
"R3QPI.RxR_OCCUPANCY.DRS": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": 0,
"Defn": "Accumulates the occupancy of a given QPI Ingress queue in each cycles. This tracks one of the three ring Ingress buffers. This can be used with the QPI Ingress Not Empty event to calculate average occupancy or the QPI Ingress Allocations event in order to calculate average queuing latency.",
"Desc": "Ingress Occupancy Accumulator",
"EvSel": 19,
"MaxIncCyc": 32,
"SubCtr": 1,
"Umask": "bxxxx1xxx",
},
"R3QPI.RxR_OCCUPANCY.SNP": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": 0,
"Defn": "Accumulates the occupancy of a given QPI Ingress queue in each cycles. This tracks one of the three ring Ingress buffers. This can be used with the QPI Ingress Not Empty event to calculate average occupancy or the QPI Ingress Allocations event in order to calculate average queuing latency.",
"Desc": "Ingress Occupancy Accumulator",
"EvSel": 19,
"MaxIncCyc": 32,
"SubCtr": 1,
"Umask": "bxxxxxx1x",
},
"R3QPI.RxR_OCCUPANCY.HOM": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": 0,
"Defn": "Accumulates the occupancy of a given QPI Ingress queue in each cycles. This tracks one of the three ring Ingress buffers. This can be used with the QPI Ingress Not Empty event to calculate average occupancy or the QPI Ingress Allocations event in order to calculate average queuing latency.",
"Desc": "Ingress Occupancy Accumulator",
"EvSel": 19,
"MaxIncCyc": 32,
"SubCtr": 1,
"Umask": "bxxxxxxx1",
},
"R3QPI.RxR_OCCUPANCY.NDR": {
"Box": "R3QPI",
"Category": "R3QPI INGRESS Events",
"Counters": 0,
"Defn": "Accumulates the occupancy of a given QPI Ingress queue in each cycles. This tracks one of the three ring Ingress buffers. This can be used with the QPI Ingress Not Empty event to calculate average occupancy or the QPI Ingress Allocations event in order to calculate average queuing latency.",
"Desc": "Ingress Occupancy Accumulator",
"EvSel": 19,
"MaxIncCyc": 32,
"SubCtr": 1,
"Umask": "bxxxxx1xx",
},
"R3QPI.TxR_CYCLES_FULL": {
"Box": "R3QPI",
"Category": "R3QPI EGRESS Events",
"Counters": "0-1",
"Defn": "Counts the number of cycles when the R2PCIe Egress buffer is full.",
"Desc": "Egress Cycles Full",
"EvSel": 37,
},
"R3QPI.TxR_CYCLES_NE": {
"Box": "R3QPI",
"Category": "R3QPI EGRESS Events",
"Counters": "0-1",
"Defn": "Counts the number of cycles when the QPI Egress is not empty. This tracks one of the three rings that are used by the QPI agent. This can be used in conjunction with the QPI Egress Occupancy Accumulator event in order to calculate average queue occupancy. Only a single Egress queue can be tracked at any given time. It is not possible to filter based on direction or polarity.",
"Desc": "Egress Cycles Not Empty",
"EvSel": 35,
},
"R3QPI.TxR_INSERTS": {
"Box": "R3QPI",
"Category": "R3QPI EGRESS Events",
"Counters": "0-1",
"Defn": "Counts the number of allocations into the QPI Egress. This tracks one of the three rings that are used by the QPI agent. This can be used in conjunction with the QPI Egress Occupancy Accumulator event in order to calculate average queue latency. Only a single Egress queue can be tracked at any given time. It is not possible to filter based on direction or polarity.",
"Desc": "Egress Allocations",
"EvSel": 36,
},
"R3QPI.TxR_NACK": {
"Box": "R3QPI",
"Category": "R3QPI EGRESS Events",
"Counters": "0-1",
"Desc": "Egress NACK",
"EvSel": 38,
},
"R3QPI.VN0_CREDITS_REJECT": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VN0_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of times a request failed to acquire a DRS VN0 credit. In order for a request to be transferred across QPI, it must be guaranteed to have a flit buffer on the remote socket to sink into. There are two credit pools, VNA and VN0. VNA is a shared pool used to achieve high performance. The VN0 pool has reserved entries for each message class and is used to prevent deadlock. Requests first attempt to acquire a VNA credit, and then fall back to VN0 if they fail. This therefore counts the number of times when a request failed to acquire either a VNA or VN0 credit and is delayed. This should generally be a rare situation.",
"Desc": "VN0 Credit Acquisition Failed on DRS",
"EvSel": 55,
},
"R3QPI.VN0_CREDITS_REJECT.NCS": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VN0_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of times a request failed to acquire a DRS VN0 credit. In order for a request to be transferred across QPI, it must be guaranteed to have a flit buffer on the remote socket to sink into. There are two credit pools, VNA and VN0. VNA is a shared pool used to achieve high performance. The VN0 pool has reserved entries for each message class and is used to prevent deadlock. Requests first attempt to acquire a VNA credit, and then fall back to VN0 if they fail. This therefore counts the number of times when a request failed to acquire either a VNA or VN0 credit and is delayed. This should generally be a rare situation.",
"Desc": "VN0 Credit Acquisition Failed on DRS",
"EvSel": 55,
"Umask": "bxx1xxxxx",
},
"R3QPI.VN0_CREDITS_REJECT.NCB": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VN0_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of times a request failed to acquire a DRS VN0 credit. In order for a request to be transferred across QPI, it must be guaranteed to have a flit buffer on the remote socket to sink into. There are two credit pools, VNA and VN0. VNA is a shared pool used to achieve high performance. The VN0 pool has reserved entries for each message class and is used to prevent deadlock. Requests first attempt to acquire a VNA credit, and then fall back to VN0 if they fail. This therefore counts the number of times when a request failed to acquire either a VNA or VN0 credit and is delayed. This should generally be a rare situation.",
"Desc": "VN0 Credit Acquisition Failed on DRS",
"EvSel": 55,
"Umask": "bxxx1xxxx",
},
"R3QPI.VN0_CREDITS_REJECT.DRS": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VN0_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of times a request failed to acquire a DRS VN0 credit. In order for a request to be transferred across QPI, it must be guaranteed to have a flit buffer on the remote socket to sink into. There are two credit pools, VNA and VN0. VNA is a shared pool used to achieve high performance. The VN0 pool has reserved entries for each message class and is used to prevent deadlock. Requests first attempt to acquire a VNA credit, and then fall back to VN0 if they fail. This therefore counts the number of times when a request failed to acquire either a VNA or VN0 credit and is delayed. This should generally be a rare situation.",
"Desc": "VN0 Credit Acquisition Failed on DRS",
"EvSel": 55,
"Umask": "bxxxx1xxx",
},
"R3QPI.VN0_CREDITS_REJECT.SNP": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VN0_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of times a request failed to acquire a DRS VN0 credit. In order for a request to be transferred across QPI, it must be guaranteed to have a flit buffer on the remote socket to sink into. There are two credit pools, VNA and VN0. VNA is a shared pool used to achieve high performance. The VN0 pool has reserved entries for each message class and is used to prevent deadlock. Requests first attempt to acquire a VNA credit, and then fall back to VN0 if they fail. This therefore counts the number of times when a request failed to acquire either a VNA or VN0 credit and is delayed. This should generally be a rare situation.",
"Desc": "VN0 Credit Acquisition Failed on DRS",
"EvSel": 55,
"Umask": "bxxxxxx1x",
},
"R3QPI.VN0_CREDITS_REJECT.HOM": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VN0_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of times a request failed to acquire a DRS VN0 credit. In order for a request to be transferred across QPI, it must be guaranteed to have a flit buffer on the remote socket to sink into. There are two credit pools, VNA and VN0. VNA is a shared pool used to achieve high performance. The VN0 pool has reserved entries for each message class and is used to prevent deadlock. Requests first attempt to acquire a VNA credit, and then fall back to VN0 if they fail. This therefore counts the number of times when a request failed to acquire either a VNA or VN0 credit and is delayed. This should generally be a rare situation.",
"Desc": "VN0 Credit Acquisition Failed on DRS",
"EvSel": 55,
"Umask": "bxxxxxxx1",
},
"R3QPI.VN0_CREDITS_REJECT.NDR": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VN0_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of times a request failed to acquire a DRS VN0 credit. In order for a request to be transferred across QPI, it must be guaranteed to have a flit buffer on the remote socket to sink into. There are two credit pools, VNA and VN0. VNA is a shared pool used to achieve high performance. The VN0 pool has reserved entries for each message class and is used to prevent deadlock. Requests first attempt to acquire a VNA credit, and then fall back to VN0 if they fail. This therefore counts the number of times when a request failed to acquire either a VNA or VN0 credit and is delayed. This should generally be a rare situation.",
"Desc": "VN0 Credit Acquisition Failed on DRS",
"EvSel": 55,
"Umask": "bxxxxx1xx",
},
"R3QPI.VN0_CREDITS_USED": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VN0_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of times a VN0 credit was used on the DRS message channel. In order for a request to be transferred across QPI, it must be guaranteed to have a flit buffer on the remote socket to sink into. There are two credit pools, VNA and VN0. VNA is a shared pool used to achieve high performance. The VN0 pool has reserved entries for each message class and is used to prevent deadlock. Requests first attempt to acquire a VNA credit, and then fall back to VN0 if they fail. This counts the number of times a VN0 credit was used. Note that a single VN0 credit holds access to potentially multiple flit buffers. For example, a transfer that uses VNA could use 9 flit buffers and in that case uses 9 credits. A transfer on VN0 will only count a single credit even though it may use multiple buffers.",
"Desc": "VN0 Credit Used",
"EvSel": 54,
},
"R3QPI.VN0_CREDITS_USED.NCS": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VN0_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of times a VN0 credit was used on the DRS message channel. In order for a request to be transferred across QPI, it must be guaranteed to have a flit buffer on the remote socket to sink into. There are two credit pools, VNA and VN0. VNA is a shared pool used to achieve high performance. The VN0 pool has reserved entries for each message class and is used to prevent deadlock. Requests first attempt to acquire a VNA credit, and then fall back to VN0 if they fail. This counts the number of times a VN0 credit was used. Note that a single VN0 credit holds access to potentially multiple flit buffers. For example, a transfer that uses VNA could use 9 flit buffers and in that case uses 9 credits. A transfer on VN0 will only count a single credit even though it may use multiple buffers.",
"Desc": "VN0 Credit Used",
"EvSel": 54,
"Umask": "bxx1xxxxx",
},
"R3QPI.VN0_CREDITS_USED.NCB": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VN0_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of times a VN0 credit was used on the DRS message channel. In order for a request to be transferred across QPI, it must be guaranteed to have a flit buffer on the remote socket to sink into. There are two credit pools, VNA and VN0. VNA is a shared pool used to achieve high performance. The VN0 pool has reserved entries for each message class and is used to prevent deadlock. Requests first attempt to acquire a VNA credit, and then fall back to VN0 if they fail. This counts the number of times a VN0 credit was used. Note that a single VN0 credit holds access to potentially multiple flit buffers. For example, a transfer that uses VNA could use 9 flit buffers and in that case uses 9 credits. A transfer on VN0 will only count a single credit even though it may use multiple buffers.",
"Desc": "VN0 Credit Used",
"EvSel": 54,
"Umask": "bxxx1xxxx",
},
"R3QPI.VN0_CREDITS_USED.DRS": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VN0_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of times a VN0 credit was used on the DRS message channel. In order for a request to be transferred across QPI, it must be guaranteed to have a flit buffer on the remote socket to sink into. There are two credit pools, VNA and VN0. VNA is a shared pool used to achieve high performance. The VN0 pool has reserved entries for each message class and is used to prevent deadlock. Requests first attempt to acquire a VNA credit, and then fall back to VN0 if they fail. This counts the number of times a VN0 credit was used. Note that a single VN0 credit holds access to potentially multiple flit buffers. For example, a transfer that uses VNA could use 9 flit buffers and in that case uses 9 credits. A transfer on VN0 will only count a single credit even though it may use multiple buffers.",
"Desc": "VN0 Credit Used",
"EvSel": 54,
"Umask": "bxxxx1xxx",
},
"R3QPI.VN0_CREDITS_USED.SNP": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VN0_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of times a VN0 credit was used on the DRS message channel. In order for a request to be transferred across QPI, it must be guaranteed to have a flit buffer on the remote socket to sink into. There are two credit pools, VNA and VN0. VNA is a shared pool used to achieve high performance. The VN0 pool has reserved entries for each message class and is used to prevent deadlock. Requests first attempt to acquire a VNA credit, and then fall back to VN0 if they fail. This counts the number of times a VN0 credit was used. Note that a single VN0 credit holds access to potentially multiple flit buffers. For example, a transfer that uses VNA could use 9 flit buffers and in that case uses 9 credits. A transfer on VN0 will only count a single credit even though it may use multiple buffers.",
"Desc": "VN0 Credit Used",
"EvSel": 54,
"Umask": "bxxxxxx1x",
},
"R3QPI.VN0_CREDITS_USED.HOM": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VN0_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of times a VN0 credit was used on the DRS message channel. In order for a request to be transferred across QPI, it must be guaranteed to have a flit buffer on the remote socket to sink into. There are two credit pools, VNA and VN0. VNA is a shared pool used to achieve high performance. The VN0 pool has reserved entries for each message class and is used to prevent deadlock. Requests first attempt to acquire a VNA credit, and then fall back to VN0 if they fail. This counts the number of times a VN0 credit was used. Note that a single VN0 credit holds access to potentially multiple flit buffers. For example, a transfer that uses VNA could use 9 flit buffers and in that case uses 9 credits. A transfer on VN0 will only count a single credit even though it may use multiple buffers.",
"Desc": "VN0 Credit Used",
"EvSel": 54,
"Umask": "bxxxxxxx1",
},
"R3QPI.VN0_CREDITS_USED.NDR": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VN0_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of times a VN0 credit was used on the DRS message channel. In order for a request to be transferred across QPI, it must be guaranteed to have a flit buffer on the remote socket to sink into. There are two credit pools, VNA and VN0. VNA is a shared pool used to achieve high performance. The VN0 pool has reserved entries for each message class and is used to prevent deadlock. Requests first attempt to acquire a VNA credit, and then fall back to VN0 if they fail. This counts the number of times a VN0 credit was used. Note that a single VN0 credit holds access to potentially multiple flit buffers. For example, a transfer that uses VNA could use 9 flit buffers and in that case uses 9 credits. A transfer on VN0 will only count a single credit even though it may use multiple buffers.",
"Desc": "VN0 Credit Used",
"EvSel": 54,
"Umask": "bxxxxx1xx",
},
"R3QPI.VNA_CREDITS_ACQUIRED": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VNA_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of QPI VNA Credit acquisitions. This event can be used in conjunction with the VNA In-Use Accumulator to calculate the average lifetime of a credit holder. VNA credits are used by all message classes in order to communicate across QPI. If a packet is unable to acquire credits, it will then attempt to use credts from the VN0 pool. Note that a single packet may require multiple flit buffers (i.e. when data is being transfered). Therefore, this event will increment by the number of credits acquired in each cycle. Filtering based on message class is not provided. One can count the number of packets transfered in a given message class using an qfclk event.",
"Desc": "VNA credit Acquisitions",
"EvSel": 51,
"MaxIncCyc": 4,
},
"R3QPI.VNA_CREDITS_REJECT": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VNA_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of attempted VNA credit acquisitions that were rejected because the VNA credit pool was full (or almost full). It is possible to filter this event by message class. Some packets use more than one flit buffer, and therefore must acquire multiple credits. Therefore, one could get a reject even if the VNA credits were not fully used up. The VNA pool is generally used to provide the bulk of the QPI bandwidth (as opposed to the VN0 pool which is used to guarantee forward progress). VNA credits can run out if the flit buffer on the receiving side starts to queue up substantially. This can happen if the rest of the uncore is unable to drain the requests fast enough.",
"Desc": "VNA Credit Reject",
"EvSel": 52,
},
"R3QPI.VNA_CREDITS_REJECT.NCS": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VNA_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of attempted VNA credit acquisitions that were rejected because the VNA credit pool was full (or almost full). It is possible to filter this event by message class. Some packets use more than one flit buffer, and therefore must acquire multiple credits. Therefore, one could get a reject even if the VNA credits were not fully used up. The VNA pool is generally used to provide the bulk of the QPI bandwidth (as opposed to the VN0 pool which is used to guarantee forward progress). VNA credits can run out if the flit buffer on the receiving side starts to queue up substantially. This can happen if the rest of the uncore is unable to drain the requests fast enough.",
"Desc": "VNA Credit Reject",
"EvSel": 52,
"Umask": "bxx1xxxxx",
},
"R3QPI.VNA_CREDITS_REJECT.NCB": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VNA_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of attempted VNA credit acquisitions that were rejected because the VNA credit pool was full (or almost full). It is possible to filter this event by message class. Some packets use more than one flit buffer, and therefore must acquire multiple credits. Therefore, one could get a reject even if the VNA credits were not fully used up. The VNA pool is generally used to provide the bulk of the QPI bandwidth (as opposed to the VN0 pool which is used to guarantee forward progress). VNA credits can run out if the flit buffer on the receiving side starts to queue up substantially. This can happen if the rest of the uncore is unable to drain the requests fast enough.",
"Desc": "VNA Credit Reject",
"EvSel": 52,
"Umask": "bxxx1xxxx",
},
"R3QPI.VNA_CREDITS_REJECT.DRS": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VNA_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of attempted VNA credit acquisitions that were rejected because the VNA credit pool was full (or almost full). It is possible to filter this event by message class. Some packets use more than one flit buffer, and therefore must acquire multiple credits. Therefore, one could get a reject even if the VNA credits were not fully used up. The VNA pool is generally used to provide the bulk of the QPI bandwidth (as opposed to the VN0 pool which is used to guarantee forward progress). VNA credits can run out if the flit buffer on the receiving side starts to queue up substantially. This can happen if the rest of the uncore is unable to drain the requests fast enough.",
"Desc": "VNA Credit Reject",
"EvSel": 52,
"Umask": "bxxxx1xxx",
},
"R3QPI.VNA_CREDITS_REJECT.SNP": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VNA_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of attempted VNA credit acquisitions that were rejected because the VNA credit pool was full (or almost full). It is possible to filter this event by message class. Some packets use more than one flit buffer, and therefore must acquire multiple credits. Therefore, one could get a reject even if the VNA credits were not fully used up. The VNA pool is generally used to provide the bulk of the QPI bandwidth (as opposed to the VN0 pool which is used to guarantee forward progress). VNA credits can run out if the flit buffer on the receiving side starts to queue up substantially. This can happen if the rest of the uncore is unable to drain the requests fast enough.",
"Desc": "VNA Credit Reject",
"EvSel": 52,
"Umask": "bxxxxxx1x",
},
"R3QPI.VNA_CREDITS_REJECT.HOM": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VNA_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of attempted VNA credit acquisitions that were rejected because the VNA credit pool was full (or almost full). It is possible to filter this event by message class. Some packets use more than one flit buffer, and therefore must acquire multiple credits. Therefore, one could get a reject even if the VNA credits were not fully used up. The VNA pool is generally used to provide the bulk of the QPI bandwidth (as opposed to the VN0 pool which is used to guarantee forward progress). VNA credits can run out if the flit buffer on the receiving side starts to queue up substantially. This can happen if the rest of the uncore is unable to drain the requests fast enough.",
"Desc": "VNA Credit Reject",
"EvSel": 52,
"Umask": "bxxxxxxx1",
},
"R3QPI.VNA_CREDITS_REJECT.NDR": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VNA_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of attempted VNA credit acquisitions that were rejected because the VNA credit pool was full (or almost full). It is possible to filter this event by message class. Some packets use more than one flit buffer, and therefore must acquire multiple credits. Therefore, one could get a reject even if the VNA credits were not fully used up. The VNA pool is generally used to provide the bulk of the QPI bandwidth (as opposed to the VN0 pool which is used to guarantee forward progress). VNA credits can run out if the flit buffer on the receiving side starts to queue up substantially. This can happen if the rest of the uncore is unable to drain the requests fast enough.",
"Desc": "VNA Credit Reject",
"EvSel": 52,
"Umask": "bxxxxx1xx",
},
"R3QPI.VNA_CREDIT_CYCLES_OUT": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VNA_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of QPI uclk cycles when the transmitted has no VNA credits available and therefore cannot send any requests on this channel. Note that this does not mean that no flits can be transmitted, as those holding VN0 credits will still (potentially) be able to transmit. Generally it is the goal of the uncore that VNA credits should not run out, as this can substantially throttle back useful QPI bandwidth.",
"Desc": "Cycles with no VNA credits available",
"EvSel": 49,
},
"R3QPI.VNA_CREDIT_CYCLES_USED": {
"Box": "R3QPI",
"Category": "R3QPI LINK_VNA_CREDITS Events",
"Counters": "0-1",
"Defn": "Number of QPI uclk cycles with one or more VNA credits in use. This event can be used in conjunction with the VNA In-Use Accumulator to calculate the average number of used VNA credits.",
"Desc": "Cycles with 1 or more VNA credits in use",
"EvSel": 50,
},
# CBO:
"CBO.CLOCKTICKS": {
"Box": "CBO",
"Category": "CBO UCLK Events",
"Counters": "0-3",
"Desc": "Uncore Clocks",
"EvSel": 0,
},
"CBO.COUNTER0_OCCUPANCY": {
"Box": "CBO",
"Category": "CBO OCCUPANCY Events",
"Counters": "1-3",
"Defn": "Since occupancy counts can only be captured in the Cbo's 0 counter, this event allows a user to capture occupancy related information by filtering the Cb0 occupancy count captured in Counter 0. The filtering available is found in the control register - threshold, invert and edge detect. E.g. setting threshold to 1 can effectively monitor how many cycles the monitored queue has an entry.",
"Desc": "Counter 0 Occupancy",
"EvSel": 31,
"MaxIncCyc": 20,
"SubCtr": 1,
},
"CBO.ISMQ_DRD_MISS_OCC": {
"Box": "CBO",
"Category": "CBO ISMQ Events",
"Counters": "0-1",
"EvSel": 33,
"MaxIncCyc": 20,
"SubCtr": 1,
},
"CBO.LLC_LOOKUP": {
"Box": "CBO",
"Category": "CBO CACHE Events",
"Counters": "0-1",
"Defn": "Counts the number of times the LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has numerous filters available. Note the non-standard filtering equation. This event will count requests that lookup the cache multiple times with multiple increments. One must ALWAYS set filter mask bit 0 and select a state or states to match. Otherwise, the event will count nothing. CBoGlCtrl[22:18] bits correspond to [FMESI] state.",
"Desc": "Cache Lookups",
"EvSel": 52,
"Notes": "Bit 0 of the umask must always be set for this event. This allows us to match a given state (or states). The state is programmed in Cn_MSR_PMON_BOX_FILTER.state. The state field is a bit mask, so you can select (and monitor) multiple states at a time. 0 = I (miss), 1 = S, 2 = E, 3 = M, 4 = F. For example, if you wanted to monitor F and S hits, you could set 10010b in the 5-bit state field. To monitor any lookup, set the field to 0x1F.",
},
"CBO.LLC_LOOKUP.DATA_READ": {
"Box": "CBO",
"Category": "CBO CACHE Events",
"Counters": "0-1",
"Defn": "Counts the number of times the LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has numerous filters available. Note the non-standard filtering equation. This event will count requests that lookup the cache multiple times with multiple increments. One must ALWAYS set filter mask bit 0 and select a state or states to match. Otherwise, the event will count nothing. CBoGlCtrl[22:18] bits correspond to [FMESI] state.",
"Desc": "Cache Lookups",
"EvSel": 52,
"Notes": "Bit 0 of the umask must always be set for this event. This allows us to match a given state (or states). The state is programmed in Cn_MSR_PMON_BOX_FILTER.state. The state field is a bit mask, so you can select (and monitor) multiple states at a time. 0 = I (miss), 1 = S, 2 = E, 3 = M, 4 = F. For example, if you wanted to monitor F and S hits, you could set 10010b in the 5-bit state field. To monitor any lookup, set the field to 0x1F.",
"Umask": "b00000011",
},
"CBO.LLC_LOOKUP.REMOTE_SNOOP": {
"Box": "CBO",
"Category": "CBO CACHE Events",
"Counters": "0-1",
"Defn": "Counts the number of times the LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has numerous filters available. Note the non-standard filtering equation. This event will count requests that lookup the cache multiple times with multiple increments. One must ALWAYS set filter mask bit 0 and select a state or states to match. Otherwise, the event will count nothing. CBoGlCtrl[22:18] bits correspond to [FMESI] state.",
"Desc": "Cache Lookups",
"EvSel": 52,
"Notes": "Bit 0 of the umask must always be set for this event. This allows us to match a given state (or states). The state is programmed in Cn_MSR_PMON_BOX_FILTER.state. The state field is a bit mask, so you can select (and monitor) multiple states at a time. 0 = I (miss), 1 = S, 2 = E, 3 = M, 4 = F. For example, if you wanted to monitor F and S hits, you could set 10010b in the 5-bit state field. To monitor any lookup, set the field to 0x1F.",
"Umask": "b00001001",
},
"CBO.LLC_LOOKUP.WRITE": {
"Box": "CBO",
"Category": "CBO CACHE Events",
"Counters": "0-1",
"Defn": "Counts the number of times the LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has numerous filters available. Note the non-standard filtering equation. This event will count requests that lookup the cache multiple times with multiple increments. One must ALWAYS set filter mask bit 0 and select a state or states to match. Otherwise, the event will count nothing. CBoGlCtrl[22:18] bits correspond to [FMESI] state.",
"Desc": "Cache Lookups",
"EvSel": 52,
"Notes": "Bit 0 of the umask must always be set for this event. This allows us to match a given state (or states). The state is programmed in Cn_MSR_PMON_BOX_FILTER.state. The state field is a bit mask, so you can select (and monitor) multiple states at a time. 0 = I (miss), 1 = S, 2 = E, 3 = M, 4 = F. For example, if you wanted to monitor F and S hits, you could set 10010b in the 5-bit state field. To monitor any lookup, set the field to 0x1F.",
"Umask": "b00000101",
},
"CBO.LLC_LOOKUP.NID": {
"Box": "CBO",
"Category": "CBO CACHE Events",
"Counters": "0-1",
"Defn": "Counts the number of times the LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has numerous filters available. Note the non-standard filtering equation. This event will count requests that lookup the cache multiple times with multiple increments. One must ALWAYS set filter mask bit 0 and select a state or states to match. Otherwise, the event will count nothing. CBoGlCtrl[22:18] bits correspond to [FMESI] state.",
"Desc": "Cache Lookups",
"EvSel": 52,
"Notes": "Bit 0 of the umask must always be set for this event. This allows us to match a given state (or states). The state is programmed in Cn_MSR_PMON_BOX_FILTER.state. The state field is a bit mask, so you can select (and monitor) multiple states at a time. 0 = I (miss), 1 = S, 2 = E, 3 = M, 4 = F. For example, if you wanted to monitor F and S hits, you could set 10010b in the 5-bit state field. To monitor any lookup, set the field to 0x1F.",
"Umask": "b01000001",
},
"CBO.LLC_VICTIMS": {
"Box": "CBO",
"Category": "CBO CACHE Events",
"Counters": "0-1",
"Defn": "Counts the number of lines that were victimized on a fill. This can be filtered by the state that the line was in.",
"Desc": "Lines Victimized",
"EvSel": 55,
},
"CBO.LLC_VICTIMS.MISS": {
"Box": "CBO",
"Category": "CBO CACHE Events",
"Counters": "0-1",
"Defn": "Counts the number of lines that were victimized on a fill. This can be filtered by the state that the line was in.",
"Desc": "Lines Victimized",
"EvSel": 55,
"Umask": "bxxxx1xxx",
},
"CBO.LLC_VICTIMS.NID": {
"Box": "CBO",
"Category": "CBO CACHE Events",
"Counters": "0-1",
"Defn": "Counts the number of lines that were victimized on a fill. This can be filtered by the state that the line was in.",
"Desc": "Lines Victimized",
"EvSel": 55,
"Umask": "bx1xxxxxx",
},
"CBO.LLC_VICTIMS.S_STATE": {
"Box": "CBO",
"Category": "CBO CACHE Events",
"Counters": "0-1",
"Defn": "Counts the number of lines that were victimized on a fill. This can be filtered by the state that the line was in.",
"Desc": "Lines Victimized",
"EvSel": 55,
"Umask": "bxxxxx1xx",
},
"CBO.LLC_VICTIMS.E_STATE": {
"Box": "CBO",
"Category": "CBO CACHE Events",
"Counters": "0-1",
"Defn": "Counts the number of lines that were victimized on a fill. This can be filtered by the state that the line was in.",
"Desc": "Lines Victimized",
"EvSel": 55,
"Umask": "bxxxxxx1x",
},
"CBO.LLC_VICTIMS.M_STATE": {
"Box": "CBO",
"Category": "CBO CACHE Events",
"Counters": "0-1",
"Defn": "Counts the number of lines that were victimized on a fill. This can be filtered by the state that the line was in.",
"Desc": "Lines Victimized",
"EvSel": 55,
"Umask": "bxxxxxxx1",
},
"CBO.MISC": {
"Box": "CBO",
"Category": "CBO MISC Events",
"Counters": "0-1",
"Defn": "Miscellaneous events in the Cbo.",
"Desc": "Cbo Misc",
"EvSel": 57,
},
"CBO.MISC.RFO_HIT_S": {
"Box": "CBO",
"Category": "CBO MISC Events",
"Counters": "0-1",
"Defn": "Miscellaneous events in the Cbo.",
"Desc": "Cbo Misc",
"EvSel": 57,
"Umask": "bxxxx1xxx",
},
"CBO.MISC.RSPI_WAS_FSE": {
"Box": "CBO",
"Category": "CBO MISC Events",
"Counters": "0-1",
"Defn": "Miscellaneous events in the Cbo.",
"Desc": "Cbo Misc",
"EvSel": 57,
"Umask": "bxxxxxxx1",
},
"CBO.MISC.STARTED": {
"Box": "CBO",
"Category": "CBO MISC Events",
"Counters": "0-1",
"Defn": "Miscellaneous events in the Cbo.",
"Desc": "Cbo Misc",
"EvSel": 57,
"Umask": "bxxxxx1xx",
},
"CBO.MISC.WC_ALIASING": {
"Box": "CBO",
"Category": "CBO MISC Events",
"Counters": "0-1",
"Defn": "Miscellaneous events in the Cbo.",
"Desc": "Cbo Misc",
"EvSel": 57,
"Umask": "bxxxxxx1x",
},
"CBO.RING_AD_USED": {
"Box": "CBO",
"Category": "CBO RING Events",
"Counters": "2-3",
"Defn": "Counts the number of cycles that the AD ring is being used at this ring stop. This includes when packets are passing by and when packets are being sunk, but does not include when packets are being sent from the ring stop. We really have two rings in JKT -- a clockwise ring and a counter-clockwise ring. On the left side of the ring, the \"UP\" direction is on the clockwise ring and \"DN\" is on the counter-clockwise ring. On the right side of the ring, this is reversed. The first half of the CBos are on the left side of the ring, and the 2nd half are on the right side of the ring. In other words (for example), in a 4c part, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
"Desc": "AD Ring In Use",
"EvSel": 27,
},
"CBO.RING_AD_USED.UP_ODD": {
"Box": "CBO",
"Category": "CBO RING Events",
"Counters": "2-3",
"Defn": "Counts the number of cycles that the AD ring is being used at this ring stop. This includes when packets are passing by and when packets are being sunk, but does not include when packets are being sent from the ring stop. We really have two rings in JKT -- a clockwise ring and a counter-clockwise ring. On the left side of the ring, the \"UP\" direction is on the clockwise ring and \"DN\" is on the counter-clockwise ring. On the right side of the ring, this is reversed. The first half of the CBos are on the left side of the ring, and the 2nd half are on the right side of the ring. In other words (for example), in a 4c part, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
"Desc": "AD Ring In Use",
"EvSel": 27,
"Umask": "bxxxxxx1x",
},
"CBO.RING_AD_USED.DOWN_ODD": {
"Box": "CBO",
"Category": "CBO RING Events",
"Counters": "2-3",
"Defn": "Counts the number of cycles that the AD ring is being used at this ring stop. This includes when packets are passing by and when packets are being sunk, but does not include when packets are being sent from the ring stop. We really have two rings in JKT -- a clockwise ring and a counter-clockwise ring. On the left side of the ring, the \"UP\" direction is on the clockwise ring and \"DN\" is on the counter-clockwise ring. On the right side of the ring, this is reversed. The first half of the CBos are on the left side of the ring, and the 2nd half are on the right side of the ring. In other words (for example), in a 4c part, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
"Desc": "AD Ring In Use",
"EvSel": 27,
"Umask": "bxxxx1xxx",
},
"CBO.RING_AD_USED.DOWN_EVEN": {
"Box": "CBO",
"Category": "CBO RING Events",
"Counters": "2-3",
"Defn": "Counts the number of cycles that the AD ring is being used at this ring stop. This includes when packets are passing by and when packets are being sunk, but does not include when packets are being sent from the ring stop. We really have two rings in JKT -- a clockwise ring and a counter-clockwise ring. On the left side of the ring, the \"UP\" direction is on the clockwise ring and \"DN\" is on the counter-clockwise ring. On the right side of the ring, this is reversed. The first half of the CBos are on the left side of the ring, and the 2nd half are on the right side of the ring. In other words (for example), in a 4c part, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
"Desc": "AD Ring In Use",
"EvSel": 27,
"Umask": "bxxxxx1xx",
},
"CBO.RING_AD_USED.UP_EVEN": {
"Box": "CBO",
"Category": "CBO RING Events",
"Counters": "2-3",
"Defn": "Counts the number of cycles that the AD ring is being used at this ring stop. This includes when packets are passing by and when packets are being sunk, but does not include when packets are being sent from the ring stop. We really have two rings in JKT -- a clockwise ring and a counter-clockwise ring. On the left side of the ring, the \"UP\" direction is on the clockwise ring and \"DN\" is on the counter-clockwise ring. On the right side of the ring, this is reversed. The first half of the CBos are on the left side of the ring, and the 2nd half are on the right side of the ring. In other words (for example), in a 4c part, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
"Desc": "AD Ring In Use",
"EvSel": 27,
"Umask": "bxxxxxxx1",
},
"CBO.RING_AK_USED": {
"Box": "CBO",
"Category": "CBO RING Events",
"Counters": "2-3",
"Defn": "Counts the number of cycles that the AK ring is being used at this ring stop. This includes when packets are passing by and when packets are being sunk, but does not include when packets are being sent from the ring stop.We really have two rings in JKT -- a clockwise ring and a counter-clockwise ring. On the left side of the ring, the \"UP\" direction is on the clockwise ring and \"DN\" is on the counter-clockwise ring. On the right side of the ring, this is reversed. The first half of the CBos are on the left side of the ring, and the 2nd half are on the right side of the ring. In other words (for example), in a 4c part, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
"Desc": "AK Ring In Use",
"EvSel": 28,
},
"CBO.RING_AK_USED.UP_ODD": {
"Box": "CBO",
"Category": "CBO RING Events",
"Counters": "2-3",
"Defn": "Counts the number of cycles that the AK ring is being used at this ring stop. This includes when packets are passing by and when packets are being sunk, but does not include when packets are being sent from the ring stop.We really have two rings in JKT -- a clockwise ring and a counter-clockwise ring. On the left side of the ring, the \"UP\" direction is on the clockwise ring and \"DN\" is on the counter-clockwise ring. On the right side of the ring, this is reversed. The first half of the CBos are on the left side of the ring, and the 2nd half are on the right side of the ring. In other words (for example), in a 4c part, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
"Desc": "AK Ring In Use",
"EvSel": 28,
"Umask": "bxxxxxx1x",
},
"CBO.RING_AK_USED.DOWN_ODD": {
"Box": "CBO",
"Category": "CBO RING Events",
"Counters": "2-3",
"Defn": "Counts the number of cycles that the AK ring is being used at this ring stop. This includes when packets are passing by and when packets are being sunk, but does not include when packets are being sent from the ring stop.We really have two rings in JKT -- a clockwise ring and a counter-clockwise ring. On the left side of the ring, the \"UP\" direction is on the clockwise ring and \"DN\" is on the counter-clockwise ring. On the right side of the ring, this is reversed. The first half of the CBos are on the left side of the ring, and the 2nd half are on the right side of the ring. In other words (for example), in a 4c part, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
"Desc": "AK Ring In Use",
"EvSel": 28,
"Umask": "bxxxx1xxx",
},
"CBO.RING_AK_USED.DOWN_EVEN": {
"Box": "CBO",
"Category": "CBO RING Events",
"Counters": "2-3",
"Defn": "Counts the number of cycles that the AK ring is being used at this ring stop. This includes when packets are passing by and when packets are being sunk, but does not include when packets are being sent from the ring stop.We really have two rings in JKT -- a clockwise ring and a counter-clockwise ring. On the left side of the ring, the \"UP\" direction is on the clockwise ring and \"DN\" is on the counter-clockwise ring. On the right side of the ring, this is reversed. The first half of the CBos are on the left side of the ring, and the 2nd half are on the right side of the ring. In other words (for example), in a 4c part, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
"Desc": "AK Ring In Use",
"EvSel": 28,
"Umask": "bxxxxx1xx",
},
"CBO.RING_AK_USED.UP_EVEN": {
"Box": "CBO",
"Category": "CBO RING Events",
"Counters": "2-3",
"Defn": "Counts the number of cycles that the AK ring is being used at this ring stop. This includes when packets are passing by and when packets are being sunk, but does not include when packets are being sent from the ring stop.We really have two rings in JKT -- a clockwise ring and a counter-clockwise ring. On the left side of the ring, the \"UP\" direction is on the clockwise ring and \"DN\" is on the counter-clockwise ring. On the right side of the ring, this is reversed. The first half of the CBos are on the left side of the ring, and the 2nd half are on the right side of the ring. In other words (for example), in a 4c part, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
"Desc": "AK Ring In Use",
"EvSel": 28,
"Umask": "bxxxxxxx1",
},
"CBO.RING_BL_USED": {