<?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>AnalyzersのトピックDo frames actually work?</title>
    <link>https://community.intel.com/t5/Analyzers/Do-frames-actually-work/m-p/822030#M2252</link>
    <description>&lt;DIV id="_mcePaste"&gt;I have put updated example code in this thread &lt;A href="http://software.intel.com/en-us/forums/showthread.php?t=86353"&gt;http://software.intel.com/en-us/forums/showthread.php?t=86353&lt;/A&gt;for latest tool's update, but I only tested it on Windows.&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;It seems that example code can work on Linux, also. No code change is required, use -&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;BR /&gt;#icc -g matrix.c -I/opt/intel/vtune_amplifier_xe_2011/include /opt/intel/vtune_amplifier_xe_2011/lib64/libittnotify.a -lpthread -o matrix&lt;BR /&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;# amplxe-cl -version&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;Intel VTune Amplifier XE 2011 Update 8 (build 221625) Command Line Tool&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;Copyright (C) 2009-2012 Intel Corporation. All rights reserved.&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;BR /&gt;# amplxe-cl -collect hotspots -- ./matrix&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;BR /&gt;You can use amplxe-gui to check report, and select Grouping "Frame Domain / Frame / Call Stack" to see expected result.&lt;/DIV&gt;&lt;BR /&gt;&lt;DIV&gt;&lt;span class="lia-inline-image-display-wrapper"&gt;&lt;img src="https://community.intel.com/skins/images/7B13F55A7CE623EF42E69096FA81A3A1/2021_redesign/images/image_not_found.png" /&gt;&lt;/span&gt;&lt;BR /&gt;Regards, Peter&lt;/DIV&gt;</description>
    <pubDate>Wed, 16 May 2012 03:18:01 GMT</pubDate>
    <dc:creator>Peter_W_Intel</dc:creator>
    <dc:date>2012-05-16T03:18:01Z</dc:date>
    <item>
      <title>Do frames actually work?</title>
      <link>https://community.intel.com/t5/Analyzers/Do-frames-actually-work/m-p/822029#M2251</link>
      <description>I am trying to profile particular segments of my code to analyze latency on one code path. I have seen &lt;A href="http://software.intel.com/en-us/articles/use-_itt_frame_-apis-from-intel-vtune-amplifier-2011-xe-to-analyze-each-frame-in-critical-code-area/"&gt;this article&lt;/A&gt; which describes the use of User APIs to do something like this.&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;I am linking against libittnotify.a and using #include "ittnotify.h" and have no problems compiling and linking code very much like the sample code in that article:&lt;/DIV&gt;&lt;DIV&gt;[cpp]// one time
__itt_domain *example_domain = __itt_domain_create("Example domain");
example_domain-&amp;gt;flags = 1;[/cpp] &lt;/DIV&gt;&lt;DIV&gt;[cpp]// in event handler, each time it is called:
__itt_frame_begin_v3(example_domain, NULL);
// code whose latency problems I want to analyze
__itt_frame_end_v3(example_domain, NULL);[/cpp]&lt;/DIV&gt;&lt;DIV&gt;I then run my executable using amplxe-cl -collect hotspots, exercising this code path many times. However, when I launch the VTune Amplifier XE 2011 GUI (build 206420)to look at the results, if I try to change the Grouping to one of the Frame ones, it only shows "No data to show. No date is available." which is not what I would expect based on that article.&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Do frames not work on Linux? Is there something wrong with the way I setup my code? Should I be using a different version to get this to work?&lt;/DIV&gt; &lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 15 May 2012 21:26:08 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Do-frames-actually-work/m-p/822029#M2251</guid>
      <dc:creator>Michael_Greene</dc:creator>
      <dc:date>2012-05-15T21:26:08Z</dc:date>
    </item>
    <item>
      <title>Do frames actually work?</title>
      <link>https://community.intel.com/t5/Analyzers/Do-frames-actually-work/m-p/822030#M2252</link>
      <description>&lt;DIV id="_mcePaste"&gt;I have put updated example code in this thread &lt;A href="http://software.intel.com/en-us/forums/showthread.php?t=86353"&gt;http://software.intel.com/en-us/forums/showthread.php?t=86353&lt;/A&gt;for latest tool's update, but I only tested it on Windows.&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;It seems that example code can work on Linux, also. No code change is required, use -&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;BR /&gt;#icc -g matrix.c -I/opt/intel/vtune_amplifier_xe_2011/include /opt/intel/vtune_amplifier_xe_2011/lib64/libittnotify.a -lpthread -o matrix&lt;BR /&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;# amplxe-cl -version&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;Intel VTune Amplifier XE 2011 Update 8 (build 221625) Command Line Tool&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;Copyright (C) 2009-2012 Intel Corporation. All rights reserved.&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;BR /&gt;# amplxe-cl -collect hotspots -- ./matrix&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;&lt;BR /&gt;You can use amplxe-gui to check report, and select Grouping "Frame Domain / Frame / Call Stack" to see expected result.&lt;/DIV&gt;&lt;BR /&gt;&lt;DIV&gt;&lt;span class="lia-inline-image-display-wrapper"&gt;&lt;img src="https://community.intel.com/skins/images/7B13F55A7CE623EF42E69096FA81A3A1/2021_redesign/images/image_not_found.png" /&gt;&lt;/span&gt;&lt;BR /&gt;Regards, Peter&lt;/DIV&gt;</description>
      <pubDate>Wed, 16 May 2012 03:18:01 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Do-frames-actually-work/m-p/822030#M2252</guid>
      <dc:creator>Peter_W_Intel</dc:creator>
      <dc:date>2012-05-16T03:18:01Z</dc:date>
    </item>
    <item>
      <title>Do frames actually work?</title>
      <link>https://community.intel.com/t5/Analyzers/Do-frames-actually-work/m-p/822031#M2253</link>
      <description>Thanks, I'm not sure what exactly was going wrong but I retried from the ground up and it works now. However, one problem I have is that my typical frame time is substantially smaller than the sampling interval, which will remain true even if I reduce the sampling interval within reasonable bounds. I am trying to analyze scenarios where instead of my processing time being, e.g., 20us it jumps to 300us.&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Is there a way to do instrumenting/tracing profiling in VTune, or does it only do statistical/sampling profiling?Does Intel have an instrumenting/tracing profiler that works on recent versions of Linux? The PTU tools don't seem to support Linux 3.0+.&lt;/DIV&gt;</description>
      <pubDate>Wed, 16 May 2012 15:59:44 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Do-frames-actually-work/m-p/822031#M2253</guid>
      <dc:creator>Michael_Greene</dc:creator>
      <dc:date>2012-05-16T15:59:44Z</dc:date>
    </item>
    <item>
      <title>Do frames actually work?</title>
      <link>https://community.intel.com/t5/Analyzers/Do-frames-actually-work/m-p/822032#M2254</link>
      <description>Yes. The tool only does statistical sampling, no instrumenting on binary or source.</description>
      <pubDate>Thu, 17 May 2012 01:06:45 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Do-frames-actually-work/m-p/822032#M2254</guid>
      <dc:creator>Peter_W_Intel</dc:creator>
      <dc:date>2012-05-17T01:06:45Z</dc:date>
    </item>
  </channel>
</rss>

