<?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 The details may depend on the in Software Tuning, Performance Optimization &amp; Platform Monitoring</title>
    <link>https://community.intel.com/t5/Software-Tuning-Performance/About-MMIO-and-SSE-question/m-p/1159965#M7010</link>
    <description>&lt;P&gt;The details may depend on the particular chipset, but the documents I have say that accesses to this space are only allowed to be naturally aligned byte, word, and double-word accesses.&lt;/P&gt;</description>
    <pubDate>Fri, 13 Sep 2019 00:30:54 GMT</pubDate>
    <dc:creator>McCalpinJohn</dc:creator>
    <dc:date>2019-09-13T00:30:54Z</dc:date>
    <item>
      <title>About MMIO and SSE question</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/About-MMIO-and-SSE-question/m-p/1159964#M7009</link>
      <description>&lt;P&gt;Lately, I tried to map SPIBAR&amp;nbsp;space into virtual address space, and read them. It works well by reps instruction, and normal memory pointer access. However, I ran into a problem that use optimized version of memcpy, it used SSE2 instruction set. The copied content are all&amp;nbsp;0xFF. Why is that happening?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My guess is,&amp;nbsp;device mapped physical memory is different from common physical memory, it&amp;nbsp;doesn't support SSE2 instruction load / store, says, out of width --&amp;gt; so no MMIO is triggered.&lt;/P&gt;&lt;P&gt;Please correct me if I'm wrong.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 10 Sep 2019 19:11:36 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/About-MMIO-and-SSE-question/m-p/1159964#M7009</guid>
      <dc:creator>Kelvin_C_</dc:creator>
      <dc:date>2019-09-10T19:11:36Z</dc:date>
    </item>
    <item>
      <title>The details may depend on the</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/About-MMIO-and-SSE-question/m-p/1159965#M7010</link>
      <description>&lt;P&gt;The details may depend on the particular chipset, but the documents I have say that accesses to this space are only allowed to be naturally aligned byte, word, and double-word accesses.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2019 00:30:54 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/About-MMIO-and-SSE-question/m-p/1159965#M7010</guid>
      <dc:creator>McCalpinJohn</dc:creator>
      <dc:date>2019-09-13T00:30:54Z</dc:date>
    </item>
  </channel>
</rss>

