<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic VTune uses the SEP loadable in Software Tuning, Performance Optimization &amp; Platform Monitoring</title>
    <link>https://community.intel.com/t5/Software-Tuning-Performance/Arbitrary-uncore-event-collection/m-p/1052532#M4924</link>
    <description>&lt;P&gt;VTune uses the SEP loadable kernel module to enable access to the performance counters, including the uncore counters.&amp;nbsp;&amp;nbsp; Whether this constitutes "kernel modification" is a matter of semantics.&lt;/P&gt;

&lt;P&gt;Many of the uncore events can only be accessed in kernel space because the RDMSR instruction can only be executed in ring 0.&amp;nbsp; There is no way around this limitation -- it is enforced by the hardware.&amp;nbsp;&amp;nbsp; Linux supports a device driver interface to read and write the MSRs, but it is normally restricted to root access.&amp;nbsp; The situation is similar for the uncore counters based in PCI configuration space -- very primitive tools exist that can be used by users with root access to program, read, and write the uncore performance counters, but it is a lot of work.&lt;/P&gt;

&lt;P&gt;VTune can access the uncore counters on most platforms, but the details of how VTune is doing the measurements and computations are not usually obvious.&amp;nbsp;&amp;nbsp; The available events change from platform to platform and from one VTune release to another, so it is hard to be concise.&amp;nbsp; On Linux, the command "amplxe-cl -help collect" will provide a list of the available analysis types -- the ones that match your hardware platform and include "bandwidth" generally use the uncore counters.&lt;/P&gt;

&lt;P&gt;VTune supports some uncore counters on Sandy Bridge processors and a lot more on Ivy Bridge and Haswell processors.&lt;/P&gt;</description>
    <pubDate>Mon, 10 Nov 2014 23:39:02 GMT</pubDate>
    <dc:creator>McCalpinJohn</dc:creator>
    <dc:date>2014-11-10T23:39:02Z</dc:date>
    <item>
      <title>Arbitrary uncore event collection</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/Arbitrary-uncore-event-collection/m-p/1052531#M4923</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;

&lt;P&gt;Hello what are possible ways to do uncore events collection?&lt;/P&gt;

&lt;P&gt;I would prefer VTune or SEP is it possible with these tools?&lt;/P&gt;

&lt;P&gt;What are other options without kernel modification?&lt;/P&gt;

&lt;P&gt;Thanks,&lt;/P&gt;

&lt;P&gt;Alexander&lt;/P&gt;</description>
      <pubDate>Mon, 10 Nov 2014 19:22:37 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/Arbitrary-uncore-event-collection/m-p/1052531#M4923</guid>
      <dc:creator>Alexander_Alexeev</dc:creator>
      <dc:date>2014-11-10T19:22:37Z</dc:date>
    </item>
    <item>
      <title>VTune uses the SEP loadable</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/Arbitrary-uncore-event-collection/m-p/1052532#M4924</link>
      <description>&lt;P&gt;VTune uses the SEP loadable kernel module to enable access to the performance counters, including the uncore counters.&amp;nbsp;&amp;nbsp; Whether this constitutes "kernel modification" is a matter of semantics.&lt;/P&gt;

&lt;P&gt;Many of the uncore events can only be accessed in kernel space because the RDMSR instruction can only be executed in ring 0.&amp;nbsp; There is no way around this limitation -- it is enforced by the hardware.&amp;nbsp;&amp;nbsp; Linux supports a device driver interface to read and write the MSRs, but it is normally restricted to root access.&amp;nbsp; The situation is similar for the uncore counters based in PCI configuration space -- very primitive tools exist that can be used by users with root access to program, read, and write the uncore performance counters, but it is a lot of work.&lt;/P&gt;

&lt;P&gt;VTune can access the uncore counters on most platforms, but the details of how VTune is doing the measurements and computations are not usually obvious.&amp;nbsp;&amp;nbsp; The available events change from platform to platform and from one VTune release to another, so it is hard to be concise.&amp;nbsp; On Linux, the command "amplxe-cl -help collect" will provide a list of the available analysis types -- the ones that match your hardware platform and include "bandwidth" generally use the uncore counters.&lt;/P&gt;

&lt;P&gt;VTune supports some uncore counters on Sandy Bridge processors and a lot more on Ivy Bridge and Haswell processors.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Nov 2014 23:39:02 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/Arbitrary-uncore-event-collection/m-p/1052532#M4924</guid>
      <dc:creator>McCalpinJohn</dc:creator>
      <dc:date>2014-11-10T23:39:02Z</dc:date>
    </item>
    <item>
      <title>Hi Alexander,</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/Arbitrary-uncore-event-collection/m-p/1052533#M4925</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN style="font-size: 12px; line-height: 18px;"&gt;Alexander,&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;&lt;SPAN style="font-size: 12px; line-height: 18px;"&gt;did you have a look at the "emon" utility that VTune provides? (in the bin32/bin64 directory) I don't know if it works for uncore events though.&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;&lt;SPAN style="font-size: 12px; line-height: 18px;"&gt;Best regards,&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;&lt;SPAN style="font-size: 12px; line-height: 18px;"&gt;Roman&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Dec 2014 14:42:56 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/Arbitrary-uncore-event-collection/m-p/1052533#M4925</guid>
      <dc:creator>Roman_D_Intel</dc:creator>
      <dc:date>2014-12-23T14:42:56Z</dc:date>
    </item>
  </channel>
</rss>

