2 use analyzer
2.1 general
Use the analyzer after executing the application on the simulator. When the simulator executes the target application, it generates one or more data files containing analysis information. After the simulation, the profiler inputs the generated profile data file and displays the profiling information.
The analyzer runs as a stand-alone graphics application. It provides a perspective based user interface that enables users to select and graphically display various types of profile information.
The analyzer can choose to dump the analysis data file in human readable format or compressed binary format for use with other software tools.
2.2 creating profile data files
Before profiling an application, you must create a profile data file for it.
To create a profile data file for the target application, simulate the application using the command option -- qprof. For more information, see the Hexagon simulator user's Guide.
be careful --qprof The specified profile must contain instructions for the type of profile information to view in the analyzer.
2.3 start the analyzer
To start the analyzer from the command line, type:
hexagon-profiler-gui [option...]
This command starts the analyzer application.
The parser accepts one or more input files on the command line. These files are specified as command options.
Command switches are used to specify command options (section 2.3.1). A switch consists of one or two dash characters followed by a switch name and parameters. Note that switch names are case sensitive. Switches must be separated by at least one space. For example:
hexagon-profiler-gui --qproffile qprof001.out --symfile app
To list the available command options, use the -- help option:
hexagon-profiler-gui --help
The analyzer displays the correct command line syntax on the console, followed by a list of available command options.
Command line defaults
If input files are not specified as command options, the analyzer assumes that you will specify them using the application menu commands:
- Select open from the analyzer's File menu.
- Use the dialog box to select a file.
2.3. 1 analyzer options
Analyzer options are used to control analyzer functions from the command line. They are specified by the command switches listed below.
Note that some options have alternate abbreviated switches defined for ease of use.
--help | -h --version | -v --qproffile filename --symfile filename --dump filename --dumpcyclefilter startcycle-endcycle --workingset filename --workingsetcyclefilter startcycle-endcycle --workingsetsymfile filename
2.3. 1.1 display information
--help -h Display the analyzer command options and exit. --version -v Display the release version of the analyzer and exit.
Note that these options are used as unique command parameters and do not start the analyzer.
2.3. 1.2 configuration file data file
--qproffile filename
Loads profile information from the specified profile data file. A space must appear after the switch name.
If multiple profile data files are generated for a single application, you can only use this option to specify the name of the first profile data file (for example qprof001.out)— Profiles automatically search for any other profile data files.
For more information about multiple profile data files, see Hexagon Simulator User guide.
Example:
hexagon-profiler-gui --qproffile qprof001.out --symfile my_app
2.3. 1.3 symbol file
--symfile filename
Loads symbols from the specified binary file. A space must appear after the switch name.
The symbols defined in the binary file are used to display the configuration file information of the application. Depending on the application type, you may need to specify multiple files as symbol files. For example:
hexagon-profiler-gui --qproffile qprof.out --symfile app1 --symfile server
Table 2-1 Lists which must be specified as stand-alone and RTOS The symbol file for the application.
2.3. 1.4 dump configuration file data
--dump filename
Dump by --qproffile Option 2.3.1.2 Section) the contents of the specified profile data file.
The specified file is a dump configuration file that contains options for specifying the format of the generated dump file. For more information, see Section 2.4.1 Festival.
The dump file format can be human readable or a compressed binary format used with other software tools.
-dumpcyclefilter startcycle-endcycle
Limits the dump of configuration file data to a specified processor cycle. Spaces cannot appear between dashes and circular values.
This option is always associated with --dump Option. It enables the user to run the entire simulation and then extract selected parts of the profile data for dump.
Profile Data dump starts when the program executes the specified start cycle and continues until the program executes the specified stop cycle.
If this option is not specified,--dump Option dumps the entire profile data file.
Note: these options are only used to dump the contents of the configuration file data file - They do not launch the profile user interface
2.3. 1.5 output Workset data
--workingset filename
Output Workset data.
The specified file is a Workset configuration file that contains options for specifying where to generate Workset data and write output. For more information, see Section 2.5 Festival.
-workingsetcyclefilter startcycle-endcycle
Limits Workset data generation to the specified processor cycles. Spaces cannot appear between dashes and circular values.
This option is always associated with --workingset Option. It enables the user to run the entire simulation and then extract Workset data from selected parts of the profile data.
The generation of working set data starts from the specified start cycle of program execution and continues to the specified stop cycle of program execution.
If this option is not specified, the --workingset Option generates Workset data from the entire profile data file.
--workingsetsymfile filename
Adds a user specified data symbol for generating Workset data.
The specified file is a symbol definition file that contains user-defined symbols for the data area in the profile data. For more information, see Section 2.5 section
Note: these options are only used to output Workset data -- they do not launch the analyzer user interface.