User Guide

Contents

report

Generate a specified type of report from an analysis result.

Syntax

-report
<report_name>
-R
<report_name>
Arguments
Argument
Description
<report_name>
Type of report to create.
Value
Description
affinity
Display binding of a thread to a range of sockets, physical, and logical cores.
Report on the overall performance of your target.
Display collected performance metrics according to the selected analysis type and identify program units that took the most CPU time (hotspots).
Display the total number of hardware events.
Report full stack data for each hotspot function; identify the impact of each stack on the function CPU or Wait time. You can use the group-by or filter options to sort the data by:
  • callstack
  • function
  • function-callstack
Report call sequences (stacks) detected during collection phase, starting from the application root (usually, the main() function). Use this report to see the impact of program units together with their callees.
Report a call tree with the time (CPU and Wait time, if available) spent in each function and its children.
Description
Use the
report
action to generate a report from an existing result. The report type must be compatible with the analysis type used in the collection.
By default, your report is written to
stdout
. If you want to save it to a file, use the report-output action-option.
Both short names and long names are case-sensitive. For example,
-R
is the short name of the
report
action, and
-r
is the short name of the
result-dir
action-option.
To get the list of available report types, use the
vtune
-help report
command.
To display help for a specific report type, use
vtune
-help report <
report_name
>
, where
<
report_name
>
is the type of report that you want to create.
In this pair of examples, a
collect
action is used to perform a hotspots analysis for the Linux*
sample
target and write the result to the current working directory. The second command uses the
report
action to generate a
hotspots
report from the most recent result and write it to
stdout
.
vtune
-collect hotspots -- /home/test/sample
vtune
-R hotspots
Generate a hotspots report from a hotspots analysis and group data by module.
vtune
-R hotspots -result-dir r001hs -group-by module
Open source view with the hotspots performance metrics for the
foo
function and use the Windows*
C:\test\my_sources
directory to search for source files.
vtune
-R hotspots -source-object function=foo -r r001hs -source-search-dir C:\test\my_sources
Write stack information for all functions in the threading analysis result
r003tr
. The data is grouped by call stack.
vtune
-R callstacks -r r003tr -group-by callstack

Product and Performance Information

1

Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804