Ivy-Bridge-EP.md

@@ -9,9 +9,11 @@
 The input file for the events on Intel® IvyBridge EP/EN/EX can be found [here](https://github.com/rrze-likwid/likwid/blob/master/src/includes/perfmon_ivybridgeEP_events.txt). 
 
 ## Counters
+- [Core-local counters](https://github.com/rrze-likwid/likwid/wiki/Ivy-Bridge-EP#core-local-counters)
     - [Fixed-purpose counters](https://github.com/rrze-likwid/likwid/wiki/Ivy-Bridge-EP#fixed-purpose-counters)
     - [General-purpose counters](https://github.com/rrze-likwid/likwid/wiki/Ivy-Bridge-EP#general-purpose-counters)
     - [Thermal counter](https://github.com/rrze-likwid/likwid/wiki/Ivy-Bridge-EP#thermal-counter)
+- [Socket-wide counters](https://github.com/rrze-likwid/likwid/wiki/Ivy-Bridge-EP#socket-wide-counters)
     - [Power counters](https://github.com/rrze-likwid/likwid/wiki/Ivy-Bridge-EP#power-counters)
     - [Home Agent counters](https://github.com/rrze-likwid/likwid/wiki/Ivy-Bridge-EP#home-agent-counters)
     - [LLC-to-QPI interface fixed-purpose counters](https://github.com/rrze-likwid/likwid/wiki/Ivy-Bridge-EP#llc-to-qpi-interface-fixed-purpose-counters)
@@ -27,9 +29,10 @@ The input file for the events on Intel® IvyBridge EP/EN/EX can be found [her
     - [Ring-to-PCIe counters](https://github.com/rrze-likwid/likwid/wiki/Ivy-Bridge-EP#ring-to-pcie-counters)
     - [IRP box counters](https://github.com/rrze-likwid/likwid/wiki/Ivy-Bridge-EP#irp-box-counters)
 
-### Fixed-purpose counters
-Since the Core2 microarchitecture, Intel® provides a set of fixed-purpose counters. Each can measure only one specific event. They are core-local, hence each hardware thread has its own set of fixed counters.
-#### Counters
+### Core-local counters
+#### Fixed-purpose counters
+Since the Core2 microarchitecture, Intel® provides a set of fixed-purpose counters. Each can measure only one specific event.
+##### Counters
 <TABLE>
 <TR>
   <TH>Counter name</TH>
@@ -48,7 +51,7 @@ Since the Core2 microarchitecture, Intel&reg; provides a set of fixed-purpose co
   <TD>CPU_CLK_UNHALTED_REF</TD>
 </TR>
 </TABLE>
-#### Available Options
+##### Available Options
 <TABLE>
 <TR>
   <TH>Option</TH>
@@ -70,9 +73,9 @@ Since the Core2 microarchitecture, Intel&reg; provides a set of fixed-purpose co
 </TR>
 </TABLE>
 
-### General-purpose counters
-The Intel&reg; IvyBridge microarchitecture provides 4 general-purpose counters consisting of a config and a counter register. They are core-local, hence each hardware thread has its own set of general-purpose counters.
-#### Counters
+#### General-purpose counters
+The Intel&reg; IvyBridge microarchitecture provides 4 general-purpose counters consisting of a config and a counter register.
+##### Counters
 <TABLE>
 <TR>
   <TH>Counter name</TH>
@@ -95,7 +98,7 @@ The Intel&reg; IvyBridge microarchitecture provides 4 general-purpose counters c
   <TD>*</TD>
 </TR>
 </TABLE>
-#### Available Options
+##### Available Options
 <TABLE>
 <TR>
   <TH>Option</TH>
@@ -134,7 +137,7 @@ The Intel&reg; IvyBridge microarchitecture provides 4 general-purpose counters c
   <TD></TD>
 </TR>
 </TABLE>
-#### Special handling for events
+##### Special handling for events
 The Intel&reg; 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&reg; 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:
 <TABLE>
 <TR>
@@ -147,19 +150,19 @@ The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measureing of offco
   <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&reg;.com/content/www/us/en/processors/architectures-software-developer-manuals.html">Intel&reg; Software Developer System Programming Manual, Vol. 3, Chapter Performance Monitoring</A> and the event files at <A HREF="https://download.01.org/perfmon/IVT">https://download.01.org/perfmon/IVT</A>.</TD>
+  <TD>Check the <A HREF="http://www.Intel&reg;.com/content/www/us/en/processors/architectures-software-developer-manuals.html">Intel&reg; 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&reg;.com/content/www/us/en/processors/architectures-software-developer-manuals.html">Intel&reg; Software Developer System Programming Manual, Vol. 3, Chapter Performance Monitoring</A> and the event files at <A HREF="https://download.01.org/perfmon/IVT">https://download.01.org/perfmon/IVT</A>.</TD>
+  <TD>Check the <A HREF="http://www.Intel&reg;.com/content/www/us/en/processors/architectures-software-developer-manuals.html">Intel&reg; 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>
 
-### Thermal counter
+#### Thermal counter
 The Intel&reg; IvyBridge microarchitecture provides one register for the current core temperature.
-#### Counters
+##### Counters
 <TABLE>
 <TR>
   <TH>Counter name</TH>
@@ -171,9 +174,10 @@ The Intel&reg; IvyBridge microarchitecture provides one register for the current
 </TR>
 </TABLE>
 
-### Power counters
-The Intel&reg; IvyBridge microarchitecture provides measurements of the current power consumption through the RAPL interface. The counters are available for one hardware thread per CPU socket.
-#### Counters
+### Socket-wide counters
+#### Power counters
+The Intel&reg; IvyBridge microarchitecture provides measurements of the current power consumption through the RAPL interface.
+##### Counters
 <TABLE>
 <TR>
   <TH>Counter name</TH>
@@ -197,11 +201,12 @@ The Intel&reg; IvyBridge microarchitecture provides measurements of the current
 </TR>
 </TABLE>
 
-### Home Agent counters
-The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the Home Agent (HA) in the Uncore. The description from Intel&reg;:<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&reg; 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 where this functional unit is called BBOX.
-#### Counters
+#### Home Agent counters
+The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the Home Agent (HA) in the uncore. The description from Intel&reg;:<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&reg; 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 Home Agent 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.
+##### Counters
 <TABLE>
 <TR>
   <TH>Counter name</TH>
@@ -224,7 +229,7 @@ The HA hardware performance counters are exposed to the operating system through
   <TD>*</TD>
 </TR>
 </TABLE>
-#### Available Options
+##### Available Options
 <TABLE>
 <TR>
   <TH>Option</TH>
@@ -254,7 +259,7 @@ The HA hardware performance counters are exposed to the operating system through
   <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&reg;.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel&reg; Xeon E5-2600 v2 Uncore Manual</A>.</TD>
+  <TD>A table of all valid opcodes can be found in the <A HREF="http://www.Intel&reg;.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel&reg; Xeon E5-2600 v2 uncore Manual</A>.</TD>
 </TR>
 <TR>
   <TD>match0</TD>
@@ -264,12 +269,12 @@ The HA hardware performance counters are exposed to the operating system through
 </TR>
 </TABLE>
 
-### LLC-to-QPI interface fixed-purpose counters
-The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the QPI Link layer (QPI) in the Uncore. The description from Intel&reg;:<BR>
+#### LLC-to-QPI interface fixed-purpose counters
+The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the QPI Link layer (QPI) in the uncore. The description from Intel&reg;:<BR>
 <I>The Intel&reg; 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&reg; QPI caching agent(s). It is responsible for converting CBo requests to Intel&reg; QPI messages (i.e. snoop generation and data response messages from the snoop response) as well as converting/forwarding ring messages to Intel&reg; QPI packets and vice versa. On Ivy Bridge, Intel&reg; QPI is split into two separate layers. The Intel&reg; QPI LL (link layer) is responsible for generating, transmitting, and receiving packets with the Intel&reg; QPI link.
 </I><BR>
-The QPI hardware performance counters are exposed to the operating system through PCI interfaces. There are maximally three of those interfaces for the QPI. If your system has not all interfaces but interface 0 does not work, try the other ones. Each interface offers an fixed-purpose counter to expose the QPI rate in GT/s. The name SBOX originates from the Nehalem EX Uncore monitoring where this functional unit is called SBOX.
-#### Counters
+The QPI hardware performance counters are exposed to the operating system through PCI interfaces. There are maximally three of those interfaces for the QPI. If your system has not all interfaces but interface 0 does not work, try the other ones. Each interface offers an fixed-purpose counter to expose the QPI rate in GT/s. The name SBOX originates from the Nehalem EX uncore monitoring.
+##### Counters
 <TABLE>
 <TR>
   <TH>Counter name</TH>
@@ -281,12 +286,12 @@ The QPI hardware performance counters are exposed to the operating system throug
 </TR>
 </TABLE>
 
-### LLC-to-QPI interface general-purpose counters
-The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the QPI Link layer (QPI) in the Uncore. The description from Intel&reg;:<BR>
+#### LLC-to-QPI interface general-purpose counters
+The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the QPI Link layer (QPI) in the uncore. The description from Intel&reg;:<BR>
 <I>The Intel&reg; 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&reg; QPI caching agent(s). It is responsible for converting CBo requests to Intel&reg; QPI messages (i.e. snoop generation and data response messages from the snoop response) as well as converting/forwarding ring messages to Intel&reg; QPI packets and vice versa. On Ivy Bridge, Intel&reg; QPI is split into two separate layers. The Intel&reg; QPI LL (link layer) is responsible for generating, transmitting, and receiving packets with the Intel&reg; QPI link.
 </I><BR>
-The QPI hardware performance counters are exposed to the operating system through PCI interfaces. There are maximally three of those interfaces for the QPI. If your system has not all interfaces but interface 0 does not work, try the other ones. Each interface offers four general-purpose counters. The name SBOX originates from the Nehalem EX Uncore monitoring where this functional unit is called SBOX.
-#### Counters
+The QPI hardware performance counters are exposed to the operating system through PCI interfaces. There are maximally three of those interfaces for the QPI. If your system has not all interfaces but interface 0 does not work, try the other ones. Each interface offers four general-purpose counters. The name SBOX originates from the Nehalem EX uncore monitoring.
+##### Counters
 <TABLE>
 <TR>
   <TH>Counter name</TH>
@@ -310,7 +315,7 @@ The QPI hardware performance counters are exposed to the operating system throug
 </TR>
 </TABLE>
 
-#### Available Options
+##### Available Options
 <TABLE>
 <TR>
   <TH>Option</TH>
@@ -340,34 +345,35 @@ The QPI hardware performance counters are exposed to the operating system throug
   <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&reg;.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel&reg; Xeon E5-2600 v2 Uncore Manual</A>.</TD>
+  <TD>A description of matching capabilities can be found in the <A HREF="http://www.Intel&reg;.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel&reg; 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&reg;.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel&reg; Xeon E5-2600 v2 Uncore Manual</A>.</TD>
+  <TD>A description of matching capabilities can be found in the <A HREF="http://www.Intel&reg;.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel&reg; 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&reg;.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel&reg; Xeon E5-2600 v2 Uncore Manual</A>.</TD>
+  <TD>A description of masking capabilities can be found in the <A HREF="http://www.Intel&reg;.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel&reg; 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&reg;.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel&reg; Xeon E5-2600 v2 Uncore Manual</A>.</TD>
+  <TD>A description of masking capabilities can be found in the <A HREF="http://www.Intel&reg;.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel&reg; Xeon E5-2600 v2 uncore Manual</A>.</TD>
 </TR>
 </TABLE>
 
-### Last Level cache counters
-The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the LLC coherency engine in the Uncore. The description from Intel&reg;:<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.
+#### Last Level cache counters
+The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the LLC coherency engine in the uncore. The description from Intel&reg;:<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&reg; 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 where those functional units are called CBOX.
-#### Counters
+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&reg; 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.
+##### Counters
 <TABLE>
 <TR>
   <TH>Counter name</TH>
@@ -390,7 +396,7 @@ The LLC hardware performance counters are exposed to the operating system throug
   <TD>*</TD>
 </TR>
 </TABLE>
-#### Available Options
+##### Available Options
 <TABLE>
 <TR>
   <TH>Option</TH>
@@ -414,7 +420,7 @@ The LLC hardware performance counters are exposed to the operating system throug
   <TD>tid</TD>
   <TD>5 bit hex value</TD>
   <TD>Set bits 0-4 in MSR_UNC_C&lt;0-15&gt;_PMON_BOX_FILTER register</TD>
-  <TD>A description of filter capabilities can be found in the <A HREF="http://www.Intel&reg;.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel&reg; Xeon E5-2600 v2 Uncore Manual</A>.</TD>
+  <TD>A description of filter capabilities can be found in the <A HREF="http://www.Intel&reg;.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel&reg; Xeon E5-2600 v2 uncore Manual</A>.</TD>
 </TR>
 <TR>
   <TD>state</TD>
@@ -432,26 +438,29 @@ The LLC hardware performance counters are exposed to the operating system throug
   <TD>opcode</TD>
   <TD>9 bit hex value</TD>
   <TD>Set bits 20-28 in MSR_UNC_C&lt;0-15&gt;_PMON_BOX_FILTER1 register</TD>
-  <TD>A table of all valid opcodes can be found in the <A HREF="http://www.Intel&reg;.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel&reg; Xeon E5-2600 v2 Uncore Manual</A>.</TD>
+  <TD>A table of all valid opcodes can be found in the <A HREF="http://www.Intel&reg;.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel&reg; 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&lt;0-15&gt;_PMON_BOX_FILTER1 register</TD>
-  <TD>A description of matching capabilities can be found in the <A HREF="http://www.Intel&reg;.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel&reg; Xeon E5-2600 v2 Uncore Manual</A>.</TD>
+  <TD>A description of matching capabilities can be found in the <A HREF="http://www.Intel&reg;.de/content/www/de/de/processors/xeon/xeon-e5-2600-v2-uncore-manual.html">Intel&reg; Xeon E5-2600 v2 uncore Manual</A>.</TD>
 </TR>
 </TABLE>
 
-#### Special handling for events
+##### Special handling for events
 The Intel&reg; 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.
 
-### Uncore management fixed-purpose counter
-The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the management box in the Uncore. The description from Intel&reg;:<BR>
-<I>The UBox serves as the system configuration controller within the physical processor.
-</I><BR>
-The Uncore management box offers one fixed-purpose counter that provides the clock frequency of the clock source of the Uncore.
-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 where those functional units are called UBOX.
-#### Counters
+#### Uncore management fixed-purpose counter
+The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the management box in the uncore. The description from Intel&reg;:<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:</I>
+- <I>The master for reading and writing physically distributed registers across physical processor using the Message Channel.</I>
+- <I>The UBox is the intermediary for interrupt traffic, receiving interrupts from the system and dispatching interrupts to the appropriate core.</I>
+- <I>The UBox serves as the system lock master used when quiescing the platform (e.g., Intel&reg; QPI bus lock).</I>
+
+The uncore management box offers one fixed-purpose counter that provides the clock frequency of the clock source of the uncore.
+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.
+##### Counters
 <TABLE>
 <TR>
   <TH>Counter name</TH>
@@ -463,12 +472,15 @@ The Uncore management performance counters are exposed to the operating system t
 </TR>
 </TABLE>
 
-### Uncore management general-purpose counters
-The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the management box in the Uncore. The description from Intel&reg;:<BR>
-<I>The UBox serves as the system configuration controller within the physical processor.
-</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 where those functional units are called UBOX.
-#### Counters
+#### Uncore management general-purpose counters
+The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the management box in the uncore. The description from Intel&reg;:<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:</I>
+- <I>The master for reading and writing physically distributed registers across physical processor using the Message Channel.</I>
+- <I>The UBox is the intermediary for interrupt traffic, receiving interrupts from the system and dispatching interrupts to the appropriate core.</I>
+- <I>The UBox serves as the system lock master used when quiescing the platform (e.g., Intel&reg; QPI bus lock).</I>
+
+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.
+##### Counters
 <TABLE>
 <TR>
   <TH>Counter name</TH>
@@ -483,7 +495,7 @@ The Uncore management performance counters are exposed to the operating system t
   <TD>*</TD>
 </TR>
 </TABLE>
-#### Available Options
+##### Available Options
 <TABLE>
 <TR>
   <TH>Option</TH>
@@ -505,14 +517,13 @@ The Uncore management performance counters are exposed to the operating system t
 </TR>
 </TABLE>
 
-### Power control unit fixed-purpose counters
-The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the power control unit (PCU) in the Uncore. The description from Intel&reg;:<BR>
-<I>The PCU is the primary Power Controller for the physical processor package.<BR>
-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.
+#### Power control unit fixed-purpose counters
+The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the power control unit (PCU) in the uncore. The description from Intel&reg;:<BR>
+<I>The PCU is the primary Power Controller for the physical processor package.<BR>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 Power control unit offers two fixed-purpose counters to retrieve the cycles CPU cores stay in state C6 and C3.
-The PCU performance counters are exposed to the operating system through the MSR interface. The name WBOX originates from the Nehalem EX Uncore monitoring where those functional units are called WBOX.
-#### Counters
+The power control unit offers two fixed-purpose counters to retrieve the cycles CPU cores stay in state C6 and C3.
+The PCU performance counters are exposed to the operating system through the MSR interface. The name WBOX originates from the Nehalem EX uncore monitoring.
+##### Counters
 <TABLE>
 <TR>
   <TH>Counter name</TH>
@@ -529,14 +540,13 @@ The PCU performance counters are exposed to the operating system through the MSR
 </TABLE>
 
 
-### Power control unit general-purpose counters
-The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the power control unit (PCU) in the Uncore. The description from Intel&reg;:<BR>
-<I>The PCU is the primary Power Controller for the physical processor package.<BR>
-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.
+#### Power control unit general-purpose counters
+The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the power control unit (PCU) in the uncore. The description from Intel&reg;:<BR>
+<I>The PCU is the primary Power Controller for the physical processor package.<BR>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 Power control unit offers four general-purpose counters. The PCU performance counters are exposed to the operating system through the MSR interface. The name WBOX originates from the Nehalem EX Uncore monitoring where those functional units are called WBOX.
+The power control unit offers four general-purpose counters. The PCU performance counters are exposed to the operating system through the MSR interface. The name WBOX originates from the Nehalem EX uncore monitoring where those functional units are called WBOX.
 
-#### Counters
+##### Counters
 <TABLE>
 <TR>
   <TH>Counter name</TH>
@@ -560,7 +570,7 @@ The Power control unit offers four general-purpose counters. The PCU performance
 </TR>
 </TABLE>
 
-#### Available Options
+##### Available Options
 <TABLE>
 <TR>
   <TH>Option</TH>
@@ -606,13 +616,13 @@ The Power control unit offers four general-purpose counters. The PCU performance
 </TR>
 </TABLE>
 
-### Memory controller fixed-purpose counters
-The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the integrated Memory Controllers (iMC) in the Uncore. The description from Intel&reg;:<BR>
+#### Memory controller fixed-purpose counters
+The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the integrated Memory Controllers (iMC) in the uncore. The description from Intel&reg;:<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.
-#### Counters
+The memory controller 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.
+##### Counters
 <TABLE>
 <TR>
   <TH>Counter name</TH>
@@ -624,13 +634,13 @@ The uncore management performance counters are exposed to the operating system t
 </TR>
 </TABLE>
 
-### Memory controller general-purpose counters
-The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the integrated Memory Controllers (iMC) in the Uncore. The description from Intel&reg;:<BR>
+#### Memory controller general-purpose counters
+The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the integrated Memory Controllers (iMC) in the uncore. The description from Intel&reg;:<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.
-#### Counters
+The memory controller 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.
+##### Counters
 <TABLE>
 <TR>
   <TH>Counter name</TH>
@@ -654,7 +664,7 @@ The uncore management performance counters are exposed to the operating system t
 </TR>
 </TABLE>
 
-#### Available Options
+##### Available Options
 <TABLE>
 <TR>
   <TH>Option</TH>
@@ -676,13 +686,13 @@ The uncore management performance counters are exposed to the operating system t
 </TR>
 </TABLE>
 
-### Ring-to-QPI counters
-The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the Ring-to-QPI (R3QPI) interface in the Uncore. The description from Intel&reg;:<BR>
+#### Ring-to-QPI counters
+The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the Ring-to-QPI (R3QPI) interface in the uncore. The description from Intel&reg;:<BR>
 <I>R3QPI is the interface between the Intel&reg; QPI Link Layer, which packetizes requests, and the Ring.<BR>
 R3QPI is the interface between the ring and the Intel&reg; QPI Link Layer. It is responsible for translating between ring protocol packets and flits that are used for transmitting data across the Intel&reg; QPI interface. It performs credit checking between the local Intel&reg; QPI LL, the remote Intel&reg; 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 where those functional units are called RBOX.
-#### Counters
+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.
+##### Counters
 <TABLE>
 <TR>
   <TH>Counter name</TH>
@@ -701,7 +711,7 @@ The R3QPI performance counters are exposed to the operating system through PCI i
   <TD>*</TD>
 </TR>
 </TABLE>
-#### Available Options
+##### Available Options
 <TABLE>
 <TR>
   <TH>Option</TH>
@@ -724,12 +734,12 @@ The R3QPI performance counters are exposed to the operating system through PCI i
 </TABLE>
 
 
-### Ring-to-PCIe counters
-The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the Ring-to-PCIe (R2PCIe) interface in the Uncore. The description from Intel&reg;:<BR>
+#### Ring-to-PCIe counters
+The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the Ring-to-PCIe (R2PCIe) interface in the uncore. The description from Intel&reg;:<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.
-#### Counters
+##### Counters
 <TABLE>
 <TR>
   <TH>Counter name</TH>
@@ -752,7 +762,7 @@ The R2PCIe performance counters are exposed to the operating system through a PC
   <TD>*</TD>
 </TR>
 </TABLE>
-#### Available Options
+##### Available Options
 <TABLE>
 <TR>
   <TH>Option</TH>
@@ -774,12 +784,12 @@ The R2PCIe performance counters are exposed to the operating system through a PC
 </TR>
 </TABLE>
 
-### IRP box counters
-The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the IRP box in the Uncore. The description from Intel&reg;:<BR>
+#### IRP box counters
+The Intel&reg; IvyBridge EP/EN/EX microarchitecture provides measurements of the IRP box in the uncore. The description from Intel&reg;:<BR>
 <I>IRP is responsible for maintaining coherency for IIO traffic that needs to be coherent (e.g. cross-socket P2P).
 </I><BR>
-The uncore management performance counters are exposed to the operating system through the PCI interface. The IBOX was introduced with the Intel&reg; IvyBridge EP/EN/EX microarchitecture.
-#### Counters
+The IRP box counters are exposed to the operating system through the PCI interface. The IBOX was introduced with the Intel&reg; IvyBridge EP/EN/EX microarchitecture.
+##### Counters
 <TABLE>
 <TR>
   <TH>Counter name</TH>
@@ -795,7 +805,7 @@ The uncore management performance counters are exposed to the operating system t
 </TR>
 </TABLE>
 
-#### Available Options
+##### Available Options
 <TABLE>
 <TR>
   <TH>Option</TH>