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
|
/*! \page ivybridgeep Intel® IvyBridge EP/EN/EX
<H1>Available performance monitors for the Intel® IvyBridge microarchitecture</H1>
<UL>
<LI>\ref IVBEP_FIXED "Fixed-purpose counters"</LI>
<LI>\ref IVBEP_PMC "General-purpose counters"</LI>
<LI>\ref IVBEP_THERMAL "Thermal counters"</LI>
<LI>\ref IVBEP_POWER "Power measurement counters"</LI>
<LI>\ref IVBEP_BBOX "Home Agent counters"</LI>
<LI>\ref IVBEP_SBOX "Intel® QPI Link Layer counters"</LI>
<LI>\ref IVBEP_CBOX "Last Level cache counters"</LI>
<LI>\ref IVBEP_UBOX "Uncore management counters"</LI>
<LI>\ref IVBEP_WBOX "Power control unit counters"</LI>
<LI>\ref IVBEP_IBOX "Coherency for IIO traffic counters"</LI>
<LI>\ref IVBEP_MBOX "Integrated memory controller counters"</LI>
<LI>\ref IVBEP_RBOX "Ring-to-QPI interface counters"</LI>
<LI>\ref IVBEP_PBOX "Ring-to-PCIe interface counters"</LI>
</UL>
<H1>Counters available for each hardware thread</H1>
\anchor IVBEP_FIXED
<H2>Fixed-purpose counters</H2>
<P>Since the Core2 microarchitecture, Intel® provides a set of fixed-purpose counters. Each can measure only one specific event.</P>
<H3>Counter and events</H3>
<TABLE>
<TR>
<TH>Counter name</TH>
<TH>Event name</TH>
</TR>
<TR>
<TD>FIXC0</TD>
<TD>INSTR_RETIRED_ANY</TD>
</TR>
<TR>
<TD>FIXC1</TD>
<TD>CPU_CLK_UNHALTED_CORE</TD>
</TR>
<TR>
<TD>FIXC2</TD>
<TD>CPU_CLK_UNHALTED_REF</TD>
</TR>
</TABLE>
<H3>Available Options</H3>
<TABLE>
<TR>
<TH>Option</TH>
<TH>Argument</TH>
<TH>Description</TH>
<TH>Comment</TH>
</TR>
<TR>
<TD>anythread</TD>
<TD>N</TD>
<TD>Set bit 2+(index*4) in config register</TD>
<TD></TD>
</TR>
<TR>
<TD>kernel</TD>
<TD>N</TD>
<TD>Set bit (index*4) in config register</TD>
<TD></TD>
</TR>
</TABLE>
\anchor IVBEP_PMC
<H2>General-purpose counters</H2>
<P>The Intel® IvyBridge EP/EN/EX microarchitecture provides 4 general-purpose counters consisting of a config and a counter register.</P>
<H3>Counter and events</H3>
<TABLE>
<TR>
<TH>Counter name</TH>
<TH>Event name</TH>
</TR>
<TR>
<TD>PMC0</TD>
<TD>*</TD>
</TR>
<TR>
<TD>PMC1</TD>
<TD>*</TD>
</TR>
<TR>
<TD>PMC2</TD>
<TD>*</TD>
</TR>
<TR>
<TD>PMC3</TD>
<TD>*</TD>
</TR>
</TABLE>
<H3>Available Options</H3>
<TABLE>
<TR>
<TH>Option</TH>
<TH>Argument</TH>
<TH>Description</TH>
<TH>Comment</TH>
</TR>
<TR>
<TD>edgedetect</TD>
<TD>N</TD>
<TD>Set bit 18 in config register</TD>
<TD></TD>
</TR>
<TR>
<TD>kernel</TD>
<TD>N</TD>
<TD>Set bit 17 in config register</TD>
<TD></TD>
</TR>
<TR>
<TD>anythread</TD>
<TD>N</TD>
<TD>Set bit 21 in config register</TD>
<TD></TD>
</TR>
<TR>
<TD>threshold</TD>
<TD>8 bit hex value</TD>
<TD>Set bits 24-31 in config register</TD>
<TD></TD>
</TR>
<TR>
<TD>invert</TD>
<TD>N</TD>
<TD>Set bit 23 in config register</TD>
<TD></TD>
</TR>
</TABLE>
<H3>Special handling for events</H3>
<P>The Intel® IvyBridge EP/EN/EX microarchitecture provides measureing of offcore events in PMC counters. Therefore the stream of offcore events must be filtered using the OFFCORE_RESPONSE registers. The Intel® IvyBridge EP/EN/EX microarchitecture has two of those registers. LIKWID defines some events that perform the filtering according to the event name. Although there are many bitmasks possible, LIKWID natively provides only the ones with response type ANY. Own filtering can be applied with the OFFCORE_RESPONSE_0_OPTIONS and OFFCORE_RESPONSE_1_OPTIONS events. Only for those events two more counter options are available:</P>
<TABLE>
<TR>
<TH>Option</TH>
<TH>Argument</TH>
<TH>Description</TH>
<TH>Comment</TH>
</TR>
<TR>
<TD>match0</TD>
<TD>16 bit hex value</TD>
<TD>Input value masked with 0x8FFF and written to bits 0-15 in the OFFCORE_RESPONSE register</TD>
<TD>Check the <A HREF="http://www.Intel®.com/content/www/us/en/processors/architectures-software-developer-manuals.html">Intel® Software Developer System Programming Manual, Vol. 3, Chapter Performance Monitoring</A> and <A HREF="https://download.01.org/perfmon/IVT">https://download.01.org/perfmon/IVT</A>.</TD>
</TR>
<TR>
<TD>match1</TD>
<TD>16 bit hex value</TD>
<TD>Input value is written to bits 16-37 in the OFFCORE_RESPONSE register</TD>
<TD>Check the <A HREF="http://www.Intel®.com/content/www/us/en/processors/architectures-software-developer-manuals.html">Intel® Software Developer System Programming Manual, Vol. 3, Chapter Performance Monitoring</A> and <A HREF="https://download.01.org/perfmon/IVT">https://download.01.org/perfmon/IVT</A>.</TD>
</TR>
</TABLE>
\anchor IVBEP_THERMAL
<H2>Thermal counter</H2>
<P>The Intel® IvyBridge EP/EN/EX microarchitecture provides one register for the current core temperature.</P>
<H3>Counter and events</H3>
<TABLE>
<TR>
<TH>Counter name</TH>
<TH>Event name</TH>
</TR>
<TR>
<TD>TMP0</TD>
<TD>TEMP_CORE</TD>
</TR>
</TABLE>
<H1>Counters available for one hardware thread per socket</H1>
\anchor IVBEP_POWER
<H2>Power counter</H2>
<P>The Intel® IvyBridge EP/EN/EX microarchitecture provides measurements of the current power consumption through the RAPL interface.</P>
<H3>Counter and events</H3>
<TABLE>
<TR>
<TH>Counter name</TH>
<TH>Event name</TH>
</TR>
<TR>
<TD>PWR0</TD>
<TD>PWR_PKG_ENERGY</TD>
</TR>
<TR>
<TD>PWR1</TD>
<TD>PWR_PP0_ENERGY</TD>
</TR>
<TR>
<TD>PWR2*</TD>
<TD>PWR_PP1_ENERGY</TD>
</TR>
<TR>
<TD>PWR3</TD>
<TD>PWR_DRAM_ENERGY</TD>
</TR>
</TABLE>
<P>*) The PWR2 counter is often not implemented by Intel® IvyBridge systems</P>
\anchor IVBEP_BBOX
<H2>Home Agent counters</H2>
<P>The Intel® IvyBridge EP/EN/EX microarchitecture provides measurements of the Home Agent (HA) in the Uncore. The description from Intel®:<BR>
<I>The HA is responsible for the protocol side of memory interactions, including coherent and non-coherent home agent protocols (as defined in the Intel® QuickPath Interconnect Specification). Additionally, the HA is responsible for ordering memory reads/writes, coming in from the modular Ring, to a given address such that the iMC (memory controller).</I><BR>
The HA hardware performance counters are exposed to the operating system through PCI interfaces. There are two of those interfaces for the HA but only for the E7-8800 v2 both are available. The name BBOX originates from the Nehalem EX Uncore monitoring.
</P>
<H3>Counter and events</H3>
<TABLE>
<TR>
<TH>Counter name</TH>
<TH>Event name</TH>
</TR>
<TR>
<TD>BBOX<0,1>C0</TD>
<TD>*</TD>
</TR>
<TR>
<TD>BBOX<0,1>C1</TD>
<TD>*</TD>
</TR>
<TR>
<TD>BBOX<0,1>C2</TD>
<TD>*</TD>
</TR>
<TR>
<TD>BBOX<0,1>C3</TD>
<TD>*</TD>
</TR>
</TABLE>
<H3>Available Options</H3>
<TABLE>
<TR>
<TH>Option</TH>
<TH>Argument</TH>
<TH>Description</TH>
<TH>Comment</TH>
</TR>
<TR>
<TD>edgedetect</TD>
<TD>N</TD>
<TD>Set bit 18 in config register</TD>
<TD></TD>
</TR>
<TR>
<TD>threshold</TD>
<TD>8 bit hex value</TD>
<TD>Set bits 24-31 in config register</TD>
<TD></TD>
</TR>
<TR>
<TD>invert</TD>
<TD>N</TD>
<TD>Set bit 23 in config register</TD>
<TD></TD>
</TR>
<TR>
<TD>opcode</TD>
<TD>6 bit hex value</TD>
<TD>Set bits 0-5 in PCI_UNC_HA_PMON_OPCODEMATCH register of PCI device</TD>
<TD>A table of all valid opcodes can be found in the <A HREF="http://www.Intel®.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel® Xeon E5-2600 v2 Uncore Manual</A>.</TD>
</TR>
<TR>
<TD>match0</TD>
<TD>46 bit hex address</TD>
<TD>Extract bits 6-31 and set bits 6-31 in PCI_UNC_HA_PMON_ADDRMATCH0 register of PCI device<BR>Extract bits 32-45 and set bits 0-13 in PCI_UNC_HA_PMON_ADDRMATCH1 register of PCI device</TD>
<TD></TD>
</TR>
</TABLE>
\anchor IVBEP_SBOX
<H2>LLC-to-QPI interface counters</H2>
<P>The Intel® IvyBridge EP/EN/EX microarchitecture provides measurements of the QPI Link layer (QPI) in the Uncore. The description from Intel®:<BR>
<I>The Intel® QPI Link Layer is responsible for packetizing requests from the caching agent on the way out to the system interface. As such, it shares responsibility with the CBo(s) as the Intel® QPI caching agent(s). It is responsible for converting CBo requests to Intel® QPI messages (i.e. snoop generation and data response messages from the snoop response) as well as converting/forwarding ring messages to Intel® QPI packets and vice versa. On Ivy Bridge, Intel® QPI is split into two separate layers. The Intel® QPI LL (link layer) is responsible for generating, transmitting, and receiving packets with the Intel® QPI link.
</I><BR>
The QPI hardware performance counters are exposed to the operating system through PCI interfaces. There are two of those interfaces for the QPI. If your system has not all interfaces but interface 0 does not work, try the other one. The name SBOX originates from the Nehalem EX Uncore monitoring.
</P>
<H3>Counter and events</H3>
<TABLE>
<TR>
<TH>Counter name</TH>
<TH>Event name</TH>
</TR>
<TR>
<TD>SBOX<0,1,2>C0</TD>
<TD>*</TD>
</TR>
<TR>
<TD>SBOX<0,1,2>C1</TD>
<TD>*</TD>
</TR>
<TR>
<TD>SBOX<0,1,2>C2</TD>
<TD>*</TD>
</TR>
<TR>
<TD>SBOX<0,1,2>C3</TD>
<TD>*</TD>
</TR>
<TR>
<TD>SBOX<0,1,2>FIX</TD>
<TD>QPI_RATE</TD>
</TR>
</TABLE>
<H3>Available Options (Only for SBOX<0-2>C<0-3> counters)</H3>
<TABLE>
<TR>
<TH>Option</TH>
<TH>Argument</TH>
<TH>Description</TH>
<TH>Comment</TH>
</TR>
<TR>
<TD>edgedetect</TD>
<TD>N</TD>
<TD>Set bit 18 in config register</TD>
<TD></TD>
</TR>
<TR>
<TD>threshold</TD>
<TD>8 bit hex value</TD>
<TD>Set bits 24-31 in config register</TD>
<TD></TD>
</TR>
<TR>
<TD>opcode</TD>
<TD>6 bit hex value</TD>
<TD>Set bits 0-5 in PCI_UNC_HA_PMON_OPCODEMATCH register of PCI device</TD>
<TD></TD>
</TR>
<TR>
<TD>match0</TD>
<TD>32 bit hex address</TD>
<TD>Input value masked with 0x8003FFF8 and written to bits 0-31 in the PCI_UNC_QPI_PMON_MATCH_0 register of PCI device</TD>
<TD>A description of matching capabilities can be found in the <A HREF="http://www.Intel®.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel® Xeon E5-2600 v2 Uncore Manual</A>.</TD>
</TR>
<TR>
<TD>match1</TD>
<TD>20 bit hex address</TD>
<TD>Input value masked with 0x000F000F and written to bits 0-19 in the PCI_UNC_QPI_PMON_MATCH_1 register of PCI device</TD>
<TD>A description of matching capabilities can be found in the <A HREF="http://www.Intel®.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel® Xeon E5-2600 v2 Uncore Manual</A>.</TD>
</TR>
<TR>
<TD>mask0</TD>
<TD>32 bit hex address</TD>
<TD>Input value masked with 0x8003FFF8 and written to bits 0-31 in the PCI_UNC_QPI_PMON_MASK_0 register of PCI device</TD>
<TD>A description of masking capabilities can be found in the <A HREF="http://www.Intel®.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel® Xeon E5-2600 v2 Uncore Manual</A>.</TD>
</TR>
<TR>
<TD>mask1</TD>
<TD>20 bit hex address</TD>
<TD>Input value masked with 0x000F000F and written to bits 0-19 in the PCI_UNC_QPI_PMON_MASK_1 register of PCI device</TD>
<TD>A description of masking capabilities can be found in the <A HREF="http://www.Intel®.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel® Xeon E5-2600 v2 Uncore Manual</A>.</TD>
</TR>
</TABLE>
\anchor IVBEP_CBOX
<H2>CBOX counter</H2>
<P>The Intel® IvyBridge EP/EN/EX microarchitecture provides measurements of the LLC coherency engine in the Uncore. The description from Intel®:<BR>
<I>The LLC coherence engine (CBo) manages the interface between the core and the last level cache (LLC). All core transactions that access the LLC are directed from the core to a CBo via the ring interconnect. The CBo is responsible for managing data delivery from the LLC to the requesting core. It is also responsible for maintaining coherence between the cores within the socket that share the LLC;
generating snoops and collecting snoop responses from the local cores when the MESIF protocol requires it.
</I><BR>
The LLC hardware performance counters are exposed to the operating system through the MSR interface. The maximal amount of supported coherency engines for the Intel® IvyBridge EP/EN/EX microarchitecture is 15. E7-8800 v2 systems have all 15 engines, the E5-2600 v2 only 10 of them and the E5-1600 v2 only 6. It may be possible that your systems does not have all CBOXes, LIKWID will skip the unavailable ones in the setup phase. The name CBOX originates from the Nehalem EX Uncore monitoring.
</P>
<H3>Counter and events</H3>
<TABLE>
<TR>
<TH>Counter name</TH>
<TH>Event name</TH>
</TR>
<TR>
<TD>CBOX<0-15>C0</TD>
<TD>*</TD>
</TR>
<TR>
<TD>CBOX<0-15>C1</TD>
<TD>*</TD>
</TR>
<TR>
<TD>CBOX<0-15>C2</TD>
<TD>*</TD>
</TR>
<TR>
<TD>CBOX<0-15>C3</TD>
<TD>*</TD>
</TR>
</TABLE>
<H3>Available Options</H3>
<TABLE>
<TR>
<TH>Option</TH>
<TH>Argument</TH>
<TH>Operation</TH>
<TH>Comment</TH>
</TR>
<TR>
<TD>edgedetect</TD>
<TD>N</TD>
<TD>Set bit 18 in config register</TD>
<TD></TD>
</TR>
<TR>
<TD>threshold</TD>
<TD>5 bit hex value</TD>
<TD>Set bits 24-28 in config register</TD>
<TD></TD>
</TR>
<TR>
<TD>tid</TD>
<TD>5 bit hex value</TD>
<TD>Set bits 0-4 in MSR_UNC_C<0-15>_PMON_BOX_FILTER register</TD>
<TD>A description of filter capabilities can be found in the <A HREF="http://www.Intel®.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel® Xeon E5-2600 v2 Uncore Manual</A>.</TD>
</TR>
<TR>
<TD>state</TD>
<TD>6 bit hex value</TD>
<TD>Set bits 17-22 in MSR_UNC_C<0-15>_PMON_BOX_FILTER register</TD>
<TD>M: 0x28, F: 0x10, M: 0x08, E: 0x04, S: 0x02, I: 0x01</TD>
</TR>
<TR>
<TD>nid</TD>
<TD>16 bit hex value</TD>
<TD>Set bits 0-15 in MSR_UNC_C<0-15>_PMON_BOX_FILTER1 register</TD>
<TD>Note: Node 0 has value 0x0001</TD>
</TR>
<TR>
<TD>opcode</TD>
<TD>9 bit hex value</TD>
<TD>Set bits 20-28 in MSR_UNC_C<0-15>_PMON_BOX_FILTER1 register</TD>
<TD>A table of all valid opcodes can be found in the <A HREF="http://www.Intel®.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel® Xeon E5-2600 v2 Uncore Manual</A>.</TD>
</TR>
<TR>
<TD>match0</TD>
<TD>2 bit hex address</TD>
<TD>Set bits 30-31 in MSR_UNC_C<0-15>_PMON_BOX_FILTER1 register</TD>
<TD>A description of matching capabilities can be found in the <A HREF="http://www.Intel®.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel® Xeon E5-2600 v2 Uncore Manual</A>.</TD>
</TR>
</TABLE>
<H3>Special handling for events</H3>
<P>The Intel® IvyBridge EP/EN/EX microarchitecture provides an event LLC_LOOKUP which can be filtered with the 'state' option. If no 'state' is set, LIKWID sets the state to 0x1F, the default value to measure all lookups.</P>
\anchor IVBEP_UBOX
<H2>Uncore management counters</H2>
<P>The Intel® IvyBridge EP/EN/EX microarchitecture provides measurements of the management box in the Uncore. The description from Intel®:<BR>
<I>
The UBox serves as the system configuration controller within the physical processor. In this capacity, the UBox acts as the central unit for a variety of functions:
<UL>
<LI>The master for reading and writing physically distributed registers across physical processor using the Message Channel.</LI>
<LI>The UBox is the intermediary for interrupt traffic, receiving interrupts from the system and dispatching interrupts to the appropriate core.</LI>
<LI>The UBox serves as the system lock master used when quiescing the platform (e.g., Intel® QPI bus lock).</LI>
</UL>
</I><BR>
The Uncore management performance counters are exposed to the operating system through the MSR interface. The name UBOX originates from the Nehalem EX Uncore monitoring.
</P>
<H3>Counter and events</H3>
<TABLE>
<TR>
<TH>Counter name</TH>
<TH>Event name</TH>
</TR>
<TR>
<TD>UBOX0</TD>
<TD>*</TD>
</TR>
<TR>
<TD>UBOX1</TD>
<TD>*</TD>
</TR>
<TR>
<TD>UBOXFIX</TD>
<TD>UBOX_CLOCKTICKS</TD>
</TR>
</TABLE>
<H3>Available Options (Only for UBOX<0,1> counters)</H3>
<TABLE>
<TR>
<TH>Option</TH>
<TH>Argument</TH>
<TH>Operation</TH>
<TH>Comment</TH>
</TR>
<TR>
<TD>edgedetect</TD>
<TD>N</TD>
<TD>Set bit 18 in config register</TD>
<TD></TD>
</TR>
<TR>
<TD>threshold</TD>
<TD>5 bit hex value</TD>
<TD>Set bits 24-28 in config register</TD>
<TD></TD>
</TR>
</TABLE>
\anchor IVBEP_WBOX
<H2>Power control unit counters</H2>
<P>The Intel® IvyBridge EP/EN/EX microarchitecture provides measurements of the power control unit (PCU) in the Uncore. The description from Intel®:<BR>
<I>The PCU is the primary Power Controller for the physical processor package. The uncore implements a power control unit acting as a core/uncore power and thermal manager. It runs its firmware on an internal micro-controller and coordinates the socket’s power states.
</I><BR>
The PCU performance counters are exposed to the operating system through the MSR interface. The name WBOX originates from the Nehalem EX Uncore monitoring.
</P>
<H3>Counter and events</H3>
<TABLE>
<TR>
<TH>Counter name</TH>
<TH>Event name</TH>
</TR>
<TR>
<TD>WBOX0</TD>
<TD>*</TD>
</TR>
<TR>
<TD>WBOX1</TD>
<TD>*</TD>
</TR>
<TR>
<TD>WBOX2</TD>
<TD>*</TD>
</TR>
<TR>
<TD>WBOX3</TD>
<TD>*</TD>
</TR>
<TR>
<TD>WBOX0FIX</TD>
<TD>CORES_IN_C3</TD>
</TR>
<TR>
<TD>WBOX1FIX</TD>
<TD>CORES_IN_C6</TD>
</TR>
</TABLE>
<H3>Available Options (Only for WBOX<0-3> counters)</H3>
<TABLE>
<TR>
<TH>Option</TH>
<TH>Argument</TH>
<TH>Operation</TH>
<TH>Comment</TH>
</TR>
<TR>
<TD>edgedetect</TD>
<TD>N</TD>
<TD>Set bit 18 in config register</TD>
<TD></TD>
</TR>
<TR>
<TD>threshold</TD>
<TD>5 bit hex value</TD>
<TD>Set bits 24-28 in config register</TD>
<TD></TD>
</TR>
<TR>
<TD>match0</TD>
<TD>32 bit hex value</TD>
<TD>Set bits 0-31 in MSR_UNC_PCU_PMON_BOX_FILTER register</TD>
<TD>Band0: bits 0-7, Band1: bits 8-15, Band2: bits 16-23, Band3: bits 24-31</TD>
</TR>
<TR>
<TD>occupancy</TD>
<TD>2 bit hex value</TD>
<TD>Set bit 14-15 in config register</TD>
<TD>Cores in C0: 0x1, in C3: 0x2, in C6: 0x3</TD>
</TR>
<TR>
<TD>occupancy_edgedetect</TD>
<TD>N</TD>
<TD>Set bit 31 in config register</TD>
<TD></TD>
</TR>
<TR>
<TD>occupancy_invert</TD>
<TD>N</TD>
<TD>Set bit 30 in config register</TD>
<TD></TD>
</TR>
</TABLE>
\anchor IVBEP_IBOX
<H2>IBOX counter</H2>
<P>The Intel® IvyBridge EP/EN/EX microarchitecture provides measurements of the IRP box in the Uncore. The description from Intel®:<BR>
<I>IRP is responsible for maintaining coherency for IIO traffic that needs to be coherent (e.g. cross-socket P2P).
</I><BR>
The IRP box counters are exposed to the operating system through the PCI interface. The IBOX was introduced with the Intel® IvyBridge EP/EN/EX microarchitecture.
</P>
<H3>Counter and events</H3>
<TABLE>
<TR>
<TH>Counter name</TH>
<TH>Event name</TH>
</TR>
<TR>
<TD>IBOX<0,1>C0</TD>
<TD>*</TD>
</TR>
<TR>
<TD>IBOX<0,1>C1</TD>
<TD>*</TD>
</TR>
</TABLE>
<H3>Available Options</H3>
<TABLE>
<TR>
<TH>Option</TH>
<TH>Argument</TH>
<TH>Operation</TH>
<TH>Comment</TH>
</TR>
<TR>
<TD>edgedetect</TD>
<TD>N</TD>
<TD>Set bit 18 in config register</TD>
<TD></TD>
</TR>
<TR>
<TD>threshold</TD>
<TD>8 bit hex value</TD>
<TD>Set bits 24-31 in config register</TD>
<TD></TD>
</TR>
</TABLE>
\anchor IVBEP_MBOX
<H2>MBOX counter</H2>
<P>The Intel® IvyBridge EP/EN/EX microarchitecture provides measurements of the integrated Memory Controllers (iMC) in the Uncore. The description from Intel®:<BR>
<I>The integrated Memory Controller provides the interface to DRAM and communicates to the rest of the uncore through the Home Agent (i.e. the iMC does not connect to the Ring).<BR>
In conjunction with the HA, the memory controller also provides a variety of RAS features, such as ECC, lockstep, memory access retry, memory scrubbing, thermal throttling, mirroring, and rank sparing.
</I><BR>
The uncore management performance counters are exposed to the operating system through PCI interfaces. There may be two memory controllers in the system (E7-8800 v2). There are 4 different PCI devices per memory controller, each covering one memory channel. Each channel has 4 different general-purpose counters and one fixed counter for the DRAM clock. The four channels of the first memory controller are MBOX0-3, the four channels of the second memory controller (if available) are named MBOX4-7. The name MBOX originates from the Nehalem EX Uncore monitoring where those functional units are called MBOX.
</P>
<H3>Counter and events</H3>
<TABLE>
<TR>
<TH>Counter name</TH>
<TH>Event name</TH>
</TR>
<TR>
<TD>MBOX<0-7>C0</TD>
<TD>*</TD>
</TR>
<TR>
<TD>MBOX<0-7>C1</TD>
<TD>*</TD>
</TR>
<TR>
<TD>MBOX<0-7>C2</TD>
<TD>*</TD>
</TR>
<TR>
<TD>MBOX<0-7>C3</TD>
<TD>*</TD>
</TR>
<TR>
<TD>MBOX<0-7>FIX</TD>
<TD>DRAM_CLOCKTICKS</TD>
</TR>
</TABLE>
<H3>Available Options (Only for counter MBOX<0-7>C<0-3>)</H3>
<TABLE>
<TR>
<TH>Option</TH>
<TH>Argument</TH>
<TH>Operation</TH>
<TH>Comment</TH>
</TR>
<TR>
<TD>edgedetect</TD>
<TD>N</TD>
<TD>Set bit 18 in config register</TD>
<TD></TD>
</TR>
<TR>
<TD>threshold</TD>
<TD>8 bit hex value</TD>
<TD>Set bits 24-31 in config register</TD>
<TD></TD>
</TR>
</TABLE>
\anchor IVBEP_RBOX
<H2>RBOX counter</H2>
<P>The Intel® IvyBridge EP/EN/EX microarchitecture provides measurements of the Ring-to-QPI (R3QPI) interface in the Uncore. The description from Intel®:<BR>
<I>R3QPI is the interface between the Intel® QPI Link Layer, which packetizes requests, and the Ring.<BR>
R3QPI is the interface between the ring and the Intel® QPI Link Layer. It is responsible for translating between ring protocol packets and flits that are used for transmitting data across the Intel® QPI interface. It performs credit checking between the local Intel® QPI LL, the remote Intel® QPI LL and other agents on the local ring.
</I><BR>
The R3QPI performance counters are exposed to the operating system through PCI interfaces. Since the RBOXes manage the traffic from the LLC-connecting ring interface on the socket with the QPI interfaces (SBOXes), the amount is similar to the amount of SBOXes. See at SBOXes how many are available for which system configuration. The name RBOX originates from the Nehalem EX Uncore monitoring.
</P>
<H3>Counter and events</H3>
<TABLE>
<TR>
<TH>Counter name</TH>
<TH>Event name</TH>
</TR>
<TR>
<TD>RBOX<0,1,2>C0</TD>
<TD>*</TD>
</TR>
<TR>
<TD>RBOX<0,1,2>C1</TD>
<TD>*</TD>
</TR>
<TR>
<TD>RBOX<0,1,2>C2</TD>
<TD>*</TD>
</TR>
</TABLE>
<H3>Available Options</H3>
<TABLE>
<TR>
<TH>Option</TH>
<TH>Argument</TH>
<TH>Operation</TH>
<TH>Comment</TH>
</TR>
<TR>
<TD>edgedetect</TD>
<TD>N</TD>
<TD>Set bit 18 in config register</TD>
<TD></TD>
</TR>
<TR>
<TD>threshold</TD>
<TD>8 bit hex value</TD>
<TD>Set bits 24-31 in config register</TD>
<TD></TD>
</TR>
</TABLE>
\anchor IVBEP_PBOX
<H2>PBOX counter</H2>
<P>The Intel® IvyBridge EP/EN/EX microarchitecture provides measurements of the Ring-to-PCIe (R2PCIe) interface in the Uncore. The description from Intel®:<BR>
<I>R2PCIe represents the interface between the Ring and IIO traffic to/from PCIe.
</I><BR>
The R2PCIe performance counters are exposed to the operating system through a PCI interface. Independent of the system's configuration, there is only one Ring-to-PCIe interface.
</P>
<H3>Counter and events</H3>
<TABLE>
<TR>
<TH>Counter name</TH>
<TH>Event name</TH>
</TR>
<TR>
<TD>PBOX0</TD>
<TD>*</TD>
</TR>
<TR>
<TD>PBOX1</TD>
<TD>*</TD>
</TR>
<TR>
<TD>PBOX2</TD>
<TD>*</TD>
</TR>
<TR>
<TD>PBOX3</TD>
<TD>*</TD>
</TR>
</TABLE>
<H3>Available Options</H3>
<TABLE>
<TR>
<TH>Option</TH>
<TH>Argument</TH>
<TH>Operation</TH>
<TH>Comment</TH>
</TR>
<TR>
<TD>edgedetect</TD>
<TD>N</TD>
<TD>Set bit 18 in config register</TD>
<TD></TD>
</TR>
<TR>
<TD>threshold</TD>
<TD>8 bit hex value</TD>
<TD>Set bits 24-31 in config register</TD>
<TD></TD>
</TR>
</TABLE>
*/
|