<?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 It can be very hard to tell in Software Tuning, Performance Optimization &amp; Platform Monitoring</title>
    <link>https://community.intel.com/t5/Software-Tuning-Performance/Utilization-vs-C0-Residency/m-p/1144460#M6725</link>
    <description>&lt;P&gt;It can be very hard to tell when documentation uses different terms as synonyms or because they are talking about different things.&lt;/P&gt;&lt;P&gt;"Core C0 Residency" seems more amenable to an unambiguous definition...&lt;/P&gt;&lt;P&gt;I usually refer to "reference cycles not halted / TSC" as "core utilization", but that is a bit sloppy.&amp;nbsp; A software-oriented person might only count "utilization" when the core is doing something useful -- for example, they might exclude time in the kernel "poll_idle()" routine.&lt;/P&gt;&lt;P&gt;The FixedCtr3 definition is not quite right when the system is configured with the FREEZE_WHILE_SMM bit is set in IA32_DEBUG_CTL (bit 14 of MSR 0x1d9).&amp;nbsp;&amp;nbsp; While servicing system management interrupts, the fixed counters will not increment, even though the processor is in C0.&lt;/P&gt;</description>
    <pubDate>Thu, 31 Jan 2019 17:15:29 GMT</pubDate>
    <dc:creator>McCalpinJohn</dc:creator>
    <dc:date>2019-01-31T17:15:29Z</dc:date>
    <item>
      <title>Utilization vs. C0 Residency</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/Utilization-vs-C0-Residency/m-p/1144459#M6724</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Core Utilization &lt;/EM&gt;and&amp;nbsp;&lt;EM&gt;Core C0 Residency&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;Seems pretty basic, but I've heard both terms used in different context, and I wonder why.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I believe they mean the same - &lt;EM&gt;number of Unhalted (C0) Cycles &lt;/EM&gt;divided by &lt;EM&gt;Potential Number of&amp;nbsp; Cycles&lt;/EM&gt;, which can be measured by FixedCtr3 / TSC.&lt;/P&gt;&lt;P&gt;Is this&amp;nbsp;true or am I missing something? is there some logical core vs. physical core&amp;nbsp;peculiarity here?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Omer&lt;/P&gt;</description>
      <pubDate>Thu, 31 Jan 2019 15:17:43 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/Utilization-vs-C0-Residency/m-p/1144459#M6724</guid>
      <dc:creator>Omer_B_Intel</dc:creator>
      <dc:date>2019-01-31T15:17:43Z</dc:date>
    </item>
    <item>
      <title>It can be very hard to tell</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/Utilization-vs-C0-Residency/m-p/1144460#M6725</link>
      <description>&lt;P&gt;It can be very hard to tell when documentation uses different terms as synonyms or because they are talking about different things.&lt;/P&gt;&lt;P&gt;"Core C0 Residency" seems more amenable to an unambiguous definition...&lt;/P&gt;&lt;P&gt;I usually refer to "reference cycles not halted / TSC" as "core utilization", but that is a bit sloppy.&amp;nbsp; A software-oriented person might only count "utilization" when the core is doing something useful -- for example, they might exclude time in the kernel "poll_idle()" routine.&lt;/P&gt;&lt;P&gt;The FixedCtr3 definition is not quite right when the system is configured with the FREEZE_WHILE_SMM bit is set in IA32_DEBUG_CTL (bit 14 of MSR 0x1d9).&amp;nbsp;&amp;nbsp; While servicing system management interrupts, the fixed counters will not increment, even though the processor is in C0.&lt;/P&gt;</description>
      <pubDate>Thu, 31 Jan 2019 17:15:29 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/Utilization-vs-C0-Residency/m-p/1144460#M6725</guid>
      <dc:creator>McCalpinJohn</dc:creator>
      <dc:date>2019-01-31T17:15:29Z</dc:date>
    </item>
  </channel>
</rss>

