<?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 Re: Software feedback:  Intel XTU - Window Timer Resolution flaw in Mobile and Desktop Processors</title>
    <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/Software-feedback-Intel-XTU-Window-Timer-Resolution-flaw/m-p/314205#M8165</link>
    <description>&lt;P&gt;Hello User2012, I would like to thank you for your feedback. I am going to share this information to the corresponding team.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards, &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 17 Sep 2014 15:45:07 GMT</pubDate>
    <dc:creator>Silvia_L_Intel1</dc:creator>
    <dc:date>2014-09-17T15:45:07Z</dc:date>
    <item>
      <title>Software feedback:  Intel XTU - Window Timer Resolution flaw</title>
      <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/Software-feedback-Intel-XTU-Window-Timer-Resolution-flaw/m-p/314204#M8164</link>
      <description>&lt;P&gt;Hey, I'm using Intel XTU and I found a flaw in the software, whenever I have the software open, even on idle, it keeps my timer set and raised to 1ms until I close the software, therefore causing a waste in power and potentially speed when the software is simply open, I see no point in having the software use a 1ms timer if all it does is update information every 1 second.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My idea is to only call TimeBeginPeriod once a stress tester or benchmark has been initialized, and call TimeEndPeriod once the benchmark/stresser is done, that way it's not unneededly keeping a raised timer resolution for no reason when the software is actually idle.  (I find it a little ironic that a piece of software meant to tweak and monitor hardware for peak performance and efficiency has a efficiency flaw in itself)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks !&lt;/P&gt;</description>
      <pubDate>Wed, 17 Sep 2014 01:51:14 GMT</pubDate>
      <guid>https://community.intel.com/t5/Mobile-and-Desktop-Processors/Software-feedback-Intel-XTU-Window-Timer-Resolution-flaw/m-p/314204#M8164</guid>
      <dc:creator>TProw</dc:creator>
      <dc:date>2014-09-17T01:51:14Z</dc:date>
    </item>
    <item>
      <title>Re: Software feedback:  Intel XTU - Window Timer Resolution flaw</title>
      <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/Software-feedback-Intel-XTU-Window-Timer-Resolution-flaw/m-p/314205#M8165</link>
      <description>&lt;P&gt;Hello User2012, I would like to thank you for your feedback. I am going to share this information to the corresponding team.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards, &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Sep 2014 15:45:07 GMT</pubDate>
      <guid>https://community.intel.com/t5/Mobile-and-Desktop-Processors/Software-feedback-Intel-XTU-Window-Timer-Resolution-flaw/m-p/314205#M8165</guid>
      <dc:creator>Silvia_L_Intel1</dc:creator>
      <dc:date>2014-09-17T15:45:07Z</dc:date>
    </item>
  </channel>
</rss>

