Processor Expert Scenarios Tool User Guide

Transcription

1 Processor Expert Scenarios Tool User Guide Doc number: CWARMv7STUG Revised: 7 August 2014

2 Freescale, Freescale logo, and CodeWarrior are trademarks of Freescale Semiconductor, Inc. All other product or service names are the property of their respective owners Freescale Semiconductor, Inc. All rights reserved. Information in this document is provided solely to enable system and software implementers to use Freescale Semiconductor products. There are no express or implied copyright licenses granted hereunder to design or fabricate any integrated circuits or integrated circuits based on the information in this document. Freescale Semiconductor reserves the right to make changes without further notice to any products herein. Freescale Semiconductor makes no warranty, representation or guarantee regarding the suitability of its products for any particular purpose, nor does Freescale Semiconductor assume any liability arising out of the application or use of any product or circuit, and specifically disclaims any and all liability, including without limitation consequential or incidental damages. Typical parameters that may be provided in Freescale Semiconductor data sheets and/or specifications can and do vary in different applications and actual performance may vary over time. All operating parameters, including Typicals, must be validated for each customer application by customer's technical experts. Freescale Semiconductor does not convey any license under its patent rights nor the rights of others. Freescale Semiconductor products are not designed, intended, or authorized for use as components in systems intended for surgical implant into the body, or other applications intended to support or sustain life, or for any other application in which the failure of the Freescale Semiconductor product could create a situation where personal injury or death may occur. Should Buyer purchase or use Freescale Semiconductor products for any such unintended or unauthorized application, Buyer shall indemnify and hold Freescale Semiconductor and its officers, employees, subsidiaries, affiliates, and distributors harmless against all claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of personal injury or death associated with such unintended or unauthorized use, even if such claim alleges that Freescale Semiconductor was negligent regarding the design or manufacture of the part. How to Contact Freescale Corporate Headquarters World Wide Web Technical Support Freescale Semiconductor, Inc William Cannon Drive West Austin, Texas U.S.A.

3 Table of Contents 1 Installing Scenarios Tool System Requirements Hardware Disk Space Supported Platforms Installing the Scenarios Tool Windows Installation Linux Installation Running the Scenario Tool Starting the Scenarios Tool Quick Start: Analyzing a Bareboard Application Create New Project and Configuration Connecting to a Board to be Analyzed Selecting a Scenario to Measure Viewing the Results Collection Compares Connection Reference Startup Options Projects Bare Board Configuration Pane Automatic Connection Discovery Modify Menu Specifying Connections Edit a Connection Modify Connection Remove a Connection Create Remote Connections Creating an Ethernet Remote Connection Creating a CodeWarrior TAP Remote Connection Creating a Gigabit TAP Remote Connection i

4 Table of Contents Creating a USB Tap Remote Connection Advanced Options Sampling Filtering Core Events Configure Target Parameters Realtime Data Visualization Enabling Realtime Data Visualization Visualizing Data Visualizing Deltas or Absolutes Filtering Graphs Toolbar Combining Graphs Updating the Y-Axis Range Custom Scenarios Modify an Existing Scenario Overview Events Metrics Initialization Scenario Reference Scenario Selection and Configuration Available Scenarios Data Display Reference Table View Data Viewing Options Exporting the Data Graph View Exporting Graphical Data Companion Graph Feature ii

5 Table of Contents 8 Linux Analysis Reference Create a Linux Application Project Profiling a Linux Application Measuring Linux Application Events Hardware Events Software Events Cache Events Selecting Events to Measure Advanced Options Environment Options Collecting the Linux Application Data Analyzing Linux Application Profiling Results Profiling a Process Profile all CPUs iii

6 Table of Contents iv

7 1 Installing Scenarios Tool The scenarios tool is available both in Windows and Linux. The installation procedure is very similar for both platforms. NOTE While the scenarios tool works in both Windows and Linux environments, all the screenshots in this document are of Windows environment. This chapter explains: System Requirements Installing the Scenarios Tool 1.1 System Requirements Hardware Windows OS: Intel Pentium 4 processor, 2 GHz or faster, Intel Xeon, Intel Core, AMD Athlon 64, AMD Opteron, or later Linux OS: 1.8 GHz Intel Pentium class processor (or better) 2 GB RAM Disk Space Disk Space 2 GB, additional space required during installation Supported Platforms Windows XP Professional (SP3), Windows 7 (32-bit and 64-bit), Windows 8, Windows 8.1 (32- bit and 64-bit) Red Hat Enterprise Linux 5.4, 32-bit and 64-bit Ubuntu (32-bit and 64-bit) OpenSUSE 12.3 (64-bit) Linux Mint 15 (32-bit and 64-bit) 5

8 Installing Scenarios Tool Installing the Scenarios Tool NOTE Some other Linux distributions may be used, but would require some manual identification and installation of the missing, required libraries. 1.2 Installing the Scenarios Tool Windows Installation The Processor Expert Scenarios Tool is delivered as a standalone executable installer. To install the product, run the installer and follow the on screen instructions. Figure 1.1 Installing the Processor Expert Scenarios 2.5 in Windows Linux Installation There is no installer available for Linux distributions. Installation of the tool is done by simply un-tarring the delivered archive into a directory of your choice and running the tool from there (instructions below). 6

9 Installing Scenarios Tool Installing the Scenarios Tool 7

10 2 Running the Scenario Tool This chapter explains how to start the Scenario Tool. This chapter explains: Starting the Scenarios Tool Quick Start: Analyzing a Bareboard Application 2.1 Starting the Scenarios Tool 1. In the directory where you have installed locate the scenariostool directory. Figure 2.1 Scenarios Tool Directory 2. To start the program, double-click on the scenariostool.exe. After starting the Scenarios Tool, if you run it for the first time, you will be asked to create a workspace. 7

11 Running the Scenario Tool Starting the Scenarios Tool Figure 2.2 New Workspace Dialog 3. If you do not want to take the default option, you can locate the workspace anywhere in the file system. To do this, click Browse and select the new location. Figure 2.3 Browse Workspace Location Dialog 4. Select the required folder or click Make New Folder to create a new folder for storing your projects. Click OK. The Select Workspace Directory dialog box closes. 5. Click OK to store the project at the specified location. The Scenarios Tool starts and displays the Welcome to Processor Expert QorIQ Scenarios Tool. 8

12 Figure 2.4 Processor Expert Scenarios Tool Splash Screen Running the Scenario Tool Starting the Scenarios Tool 6. After the program loads you are presented with the main window, where you can begin to use the program to analyze bare metal (bare board) or Linux user space applications. 7. You will see the splash screen and you will be presented with a dialog that will ask you to select your workspace. You can choose the default proposed or Browse to an area of your choice: Figure 2.5 Select a Workspace Screen 9

13 Running the Scenario Tool Quick Start: Analyzing a Bareboard Application 8. Click OK and the tool will be ready for you to work with it. 2.2 Quick Start: Analyzing a Bareboard Application From the Scenarios Tool menu bar, select New Configuration. The New Configuration window appears. From this configuration window you can choose whether you will analyze a Bareboard or Linux user space application Create New Project and Configuration Figure 2.6 Create a New Configurations Screen 1. From the File menu, select New Configuration. 2. In the Configuration name textbox, type the name of the configuration. 3. Under Measure, select Bareboard Performance events. 4. Select Create a new project radio button. 5. In the Project name textbox, type the name of the project. 6. Select Finish. 10

14 Running the Scenario Tool Quick Start: Analyzing a Bareboard Application Connecting to a Board to be Analyzed Once a project has been selected, you will now need to select a connection to the board. There are two ways to do this; one by using the Automatic Connection Discovery feature of the tool or by manually configuring the connection. In this section, the automatic detection feature of the tool is used. Refer to the reference section of the manual for more details on the Automatic Connection Discovery and the Manual Connection Configuration. Figure 2.7 Configuration Window From the Configuration Connection Tool menu bar, select Search For Connections. The Search Connections window appears and Scenarios Tool will start scanning the local network for available probes. NOTE Searching the network can be a time consuming operation and it may take a while for the available probes to be listed. Once the scan is completed, the discovered probes will be listed as shown in the Figure 2.8. Scroll through the list of probes. At this point you can select one or multiple probes. To select multiple probes, hold the control key and click through the probes. After you have completed selecting the probes, click OK to save the selections and dismiss the window. 11

15 Running the Scenario Tool Quick Start: Analyzing a Bareboard Application Figure 2.8 Search Connections Screen A list of the available probes appears. 1. Under Connection Details, select Connection. 2. Select OK. The Search Connections window closes. At this point the connection will be selected and will be reflected in the Configuration window Figure 2.9. And you will have a connection to a system. You should now scan the probe to determine the processor that is connected to the probe Selecting a Scenario to Measure From the Configuration Scenario Tool menu bar, select Add a Scenario (you can also choose the button in the Scenarios section). Only those scenarios that are applicable to the selected processor will be presented. For this particular example, a P5020 based system is being used. 12

16 Running the Scenario Tool Quick Start: Analyzing a Bareboard Application 1. The Add P5020 Scenarios window appears. Figure 2.9 Add P5020 Scenarios 2. Select the subsystem that you want to analyze. The example above shows CPU - > Cache. Refer to the Reference Section of this manual for further details on the options available in this dialog. 3. From the Scenario Tool toolbar, select File -> Save. 4. From the Scenario Tool toolbar, select Measure -> Launch. NOTE Once a scenario(s) has been chosen, note that at right Scenarios change there is a button that enables advanced actions for the collection. Pressing it will enable a checkbox next to each scenario. This checkbox when selected will disable the configuration of the appropriate hardware and will collect data. It assumes that the hardware has either been configured perhaps in a previous run or externally (for example, by instrumentation of the application in the target). 13

17 Running the Scenario Tool Quick Start: Analyzing a Bareboard Application Figure 2.10 Scenarios Advanced Option Selection Figure 2.11 Collection of Scenario Data Screen 5. Once the measurements are complete, the results will appear in the collection folder of the project folder. 6. In the Analysis Session view, you can see the overall session status. You can use the toolbar to Go, Pause, or Stop data sampling. 7. In the Progress view, you can view the detailed progress. 8. The Results are collected as part of the project and will appear (assuming the layout of the tools as the default view) in the left side of the tool. 14

18 Running the Scenario Tool Quick Start: Analyzing a Bareboard Application Viewing the Results The results can be viewed either in tabular or graphical form. To view the results: 1. In the project view, select the project you are interested in and double-click its name. 2. The generated data will appear in a tabular form as shown in Figure You can specify the names of the columns in the Display Measurements text box that you want to filter. Figure 2.12 Bareboard Results Table View 4. At the bottom of the table view, there is a toolbar having five icons: View Metric view the definitions of all the metrics that appear in the report Aliases specify alternate names to be displayed in the report labels Search Table find text in the Results table Export to CSV export the report to a text file with comma-separated values Choose Measurements select measurements to be displayed in the report and/or reorder the measurements 5. Below the toolbar, there are five tabs: Results the default view 15

19 Running the Scenario Tool Quick Start: Analyzing a Bareboard Application Graphs shows a graphical view of the data Summaries shows the summary of minimum, maximum, and average of values Configuration shows a summary of the connection to the target Notes shows the text area 6. Click the Graphs tab to view the data in graphical format. Figure 2.13 Bare Board Graphics View 7. Click the Summaries tab to view the results as bar chart having summarized values of minimum, maximum, and average. 16

20 Running the Scenario Tool Quick Start: Analyzing a Bareboard Application Figure 2.14 Summaries view 8. Click the Configuration tab to view the scenarios that are configured. For more details, refer to the Connecting to a Board to be Analyzed topic. 9. Click the Notes tab to view the text area where you can enter any information. Figure 2.15 Notes view 17

21 Running the Scenario Tool Quick Start: Analyzing a Bareboard Application Collection Compares Two performance analysis collections can be compared by selecting them in the Performance Analysis view, choosing Compare option from the context menu. To compare collections: 1. In the Performance Analysis view, select more than one scenario for comparison. 2. Right-click on the selected scenarios and select Compare option from the context menu. Figure 2.16 Performance Analysis Collection Compare 3. A Compare view will appear with three tabs: Side by Side: shows the summary computations for each collection interleaved 18

22 Figure 2.17 Performance Analysis Side by Side Comparison Running the Scenario Tool Quick Start: Analyzing a Bareboard Application Deltas: shows the difference between the summaries of each collection as a simple subtraction (C1 - C0) Percentages: show the difference between the summaries of each collection as a ratio 100*(C1 - C0)/C0 Two collections can be compared if they were created from the same scenario, or from two custom scenarios that are equivalent. 19

23 Running the Scenario Tool Quick Start: Analyzing a Bareboard Application 20

24 3 Connection Reference This chapter explains: Startup Options Projects Bare Board Configuration Pane Automatic Connection Discovery Specifying Connections Edit a Connection Create Remote Connections 3.1 Startup Options The scenarios tool uses the concept of a "workspace", which is an area in the local files system that is used to store the results. There is a default tool that is selected when the tool is started for the first time. Figure 3.1 Workspace Selection You can select a separate workspace by selecting the Browse button. 21

25 Connection Reference Projects Figure 3.2 Selection of Alternate Workspace 3.2 Projects The Scenarios Tool organizes measurement activities in terms of Projects. A project contains configuration information and the data that was collected. This is illustrated below. 22

26 Connection Reference Bare Board Configuration Pane Figure 3.3 Projects and Collections View 3.3 Bare Board Configuration Pane Use this panel to define the connection method that will be used to communicate to the target hardware when a probe is being used in Bare Board situations. 23

27 Connection Reference Bare Board Configuration Pane Figure 3.4 Bare Board Connection Configuration Table 3.1 displays the various options available on the Configuration pane. Table 3.1 Configuration Settings Option Connection Processor Status Scan Probe Description Specify connection method to target hardware in Bare Metal sessions Displays the target processor. This determines what metrics and scenarios will be available to measure Shows the availability of a selected connection. RED means that the target is unavailable ORANGE means that the status is unknown GREEN means that the target is available to use Select this to scan the connection and determine the status of the connection and the type of processor that is connected to the probe. Note: This operation can be intrusive and in some cases may cause problems in the DUT. 24

28 Connection Reference Bare Board Configuration Pane Table 3.1 Configuration Settings Option Scenarios Stop sampling after xxx Samples Description Use this to select the type of data to be collected Number of samples to be collected Table 3.2 lists and describes the Connection toolbar buttons available to work with the configuration settings. Table 3.2 Configuration Pane Connection Toolbar Buttons Option Description Pull-down menu It is blank if there are currently no selected connection. It lists the currently selected connection and will also have a list of previously selected connections. New Connection Click to open the Add a New Connection Dialog. Select this option if you want to add/configure manually a connection in a Bare Board project. Search for connections Click to open the Search the network for connections dialog box. This option will search the local subnet for available Freescale probes. Edit Connection Click to open the Edit an Existing Connection dialog box. This option will allow user to modify an existing connection. This connection can be a connection that was either automatically selected connection or one that was manually added. Remove Connection This option will allow user to remove an existing connection. 25

29 Connection Reference Automatic Connection Discovery 3.4 Automatic Connection Discovery The Connection Discovery feature will search the local network for available probes and devices connected to them. These probes will let you control software running on target hardware, with minimal intrusion into target operation. From the Connection toolbar, select Search For Connections. The Search Connections window appears and it will search the local subnet for probes. NOTE This search may take some time depending on how many probes are present in the net. Also, this search only works on a local subnet and will not work across VPN connections. Figure 3.5 Search for Connections When the search is completed, the dialog will populate the table with details of the probes that it discovered. The Connection Details column provides connection type and IP addresses of the probes that were found on the network. If you prefer the connection type and host names to be displayed in the connection details columns, select Use host names instead of IP Addresses checkbox. The Name column provides any names associated with the probe. The Processor column displays the processor that the probe is connected to. The Status column displays additional useful information about the probe. There is also the option using the drop-down button in the connection section that allows the user to display the probes information on the connection pull-down in different ways. The probe information can be displayed as: 26

30 Connection Reference Specifying Connections Figure 3.6 Probe Display Options IP Addresses Host names Aliases. By default, it is displayed by IP addresses Modify Menu To specify a connection based on the search connections, follow the below steps: 1. From the Connection toolbar, select Menu. The Menu pull-down appears. 2. Make desired changes. 3. Click OK. The new changes will appear in connection pull-down list. 3.5 Specifying Connections To specify a connection based on the search connections follow steps below: 1. From the Connection toolbar, select Search for Connections. The Search Connections window appears. 2. From Connection Type column, select the desired probe. 3. Click OK. The new connection appears in connection pull-down list. 4. Edit a connection. The edit connection feature allows the probe settings to be modified. The current settings of the probe will be displayed. From the Connection toolbar, select Edit Connection. The Edit Connection window appears. 3.6 Edit a Connection The edit connection feature allows the probe settings to be modified. The current settings of the probe will be displayed. From the Connection toolbar, select Edit Connection. The Edit Connection window appears. 27

31 Connection Reference Create Remote Connections Figure 3.7 Edit Connection Modify Connection To specify a connection based on the search connections follow steps below: 1. From the Connection toolbar, select Edit Connections. The Edit Connection window appears. 2. Make the desired changes. 3. Click OK. The new changes will appear in connection pull-down list Remove a Connection The remove connection feature deletes probes listed in the connection pull-down list. From the Connection toolbar, select Remove Connection. The selected connection will be removed from the connection list. 3.7 Create Remote Connections The CodeWarrior Ethernet TAP, Gigabit TAP, and USBTAP (called "probes" in the remaining of this document) connect to the target to control and provide visibility into your target hardware. These probes let you control software running on target hardware, with minimal intrusion into target operation. You can use the JTAG connector on your target hardware to interface with the TAP hardware. Alternatively, a software debug agent running on the QorIQ device may be used instead of a JTAG probe (TAP) Creating an Ethernet Remote Connection Follow the steps below to create an Ethernet TAP network interface to communicate with the target hardware: 28

32 Connection Reference Create Remote Connections 1. From the Connection toolbar, select New Connection. The Add a New Connection window appears. 2. From Connection Type drop-down list, select Ethernet TAP. 3. Specify the Ethernet TAP hostname or an IP address in the Hostname/IP text box. 4. Specify an alias for the Ethernet TAP in the Alias text box. 5. Click OK. The new connection appears in the project Creating a CodeWarrior TAP Remote Connection Follow the steps below to create an Ethernet TAP network interface to communicate with the target hardware: 1. From the Connection toolbar, select New Connection. The Add a New Connection window appears. 2. From Connection Type drop-down list, select CodeWarrior TAP. 3. Specify the Ethernet TAP hostname or an IP address in the Hostname/IP text box. Or, specify the USB serial number in the USB Serial # text box. 4. Specify an alias for the CodeWarrior TAP in the Alias text box. 5. Click OK. The new connection appears in the project Creating a Gigabit TAP Remote Connection Follow the steps below to create an Ethernet TAP network interface to communicate with the target hardware: 1. From the Connection toolbar, select New Connection. The Add a New Connection window appears. 2. From Connection Type drop-down list, select Gigabit TAP. 3. Specify the Ethernet TAP hostname or an IP Address in the Hostname/IP text box. 4. From the Debug Connection drop-down list, select Debug Connection. 5. Specify an alias for the CodeWarrior TAP in the Alias text box. 6. Click OK. The new connection appears in the project Creating a USB TAP Remote Connection Follow the steps below to create an USB interface to communicate with the target hardware: 1. From the Connection toolbar, select New Connection. The Add a New Connection window appears. 2. From Connection Type drop-down list, select USB TAP. 29

33 Connection Reference Create Remote Connections NOTE Make sure you have attached the USB TAP to the target hardware and to the computer hosting the Scenario Tool. 3. Specify the USB serial number in the USB Serial # text box. 4. Specify an alias for the Ethernet TAP in the Alias text box. 5. Click OK. The new connection appears in the project Creating a Remote Connection Using the Advanced Settings In certain cases, it may be required to run the Command Converter Server (CCS) or the Common Debug Development Environment agent (CDDE) on a remote machine. For an example, when targeting a device connected to a USBTAP that is connected to a remote machine. In this case, there is no direct connection from your host machine to the USBTAP. CCS needs to run on the machine that is physically connected to the USBTAP. Figure 3.8 Advanced Connection Settings As shown in the figure above, enter the hostname or the IP address of the machine that is connected to the USBTAP. As indicated by the warning message, CCS has to be manually launched on the remote machine and has to be listening for incoming connections at the specified port. When launching a CCS server manually, ensure that you use a current CCS version. If CCS is to be launched by the tool locally on your host machine, but you simply want to use a different port for CCS (the default is which falls in the ephemeral port range on Linux, and you may want to 30

34 Connection Reference Create Remote Connections avoid a conflict and chose a safer port), simply deselect the Hostname/IP option and enter the port number of your choice. NOTE When launching CCS manually, make sure to use a latest CCS version, preferably the version that is shipped with the tools. The same applies if you are launching CDDE manually Creating a Connection to a Software Debug Agent In some cases, such as when using QorIQ-based devices deployed in the field, it is not possible to connect a JTAG probe to the device. Instead, a software debug agent can be installed and run on the QorIQ Linux devices (see Installing and Running the QorIQ Software Debug Agent topic). The Packet Analysis Tool can use this agent to configure the trace settings and to retrieve the trace data at the end of the test. The agent is minimally intrusive since it is used at the beginning of the test to program the trace settings, during the test to monitor the progress and at the end of the test to retrieve the trace data. Follow the steps below to create a connection with the target device running a software debug agent: 1. From the Connection toolbar, select New Connection. The Add a New Connection window appears. 2. From Connection Type drop-down list, select Debug Agent. 3. Specify the hostname or the IP address of the QorIQ device. 4. Specify the port number used by the target debug agent. 5. Click OK. The new connection appears in the project Installing and Running the QorIQ Software Debug Agent There are three packages required in order to run the debug agent: qoriq-dbg: an updated version of the QorIQ debug file system Linux kernel module tcf-qoriqddrbuf: a Linux kernel module that provide access to the reserved memory range where the DDR trace buffer is located tcf-qoriqdbg: the debug agent that uses the two packages that is qoriq-dbg and tcfqoriqddrbuf These packages can be found in the following folder: <Packet Analysis Tool install>/packettool/ support/ These packages contain the source code, the autotool files and instructions for building. For example, assuming that your QorIQ device uses the Freescale Linux QorIQ SDK and that you have installed 31

35 Connection Reference Create Remote Connections this SDK on a x86 Linux machine, you may cross-compile the packages and install them as described below: 32

36 4 Advanced Options In addition to the Connection Option and Scenarios section, the Bare Board configuration window offers additional advanced options to control the sampling, filtering core events and to adjust several parameters from the system under test. NOTE The sampling options apply only to bare metal. This chapter contains the following sections: Sampling Filtering Core Events Configure Target Parameters Realtime Data Visualization 4.1 Sampling Normally the Scenarios Tool will start collecting data automatically. However it may be necessary to configure when to start sampling events and when to stop the collection. This may be useful in the case where the workload may need to stabilize before a measurement is made or when a user wants to collect data after some external event has occurred and there is a need to keep the last n-events. Figure 4.1 Sampling Configuration 31

37 Advanced Options Filtering Core Events 4.2 Filtering Core Events By default, the Scenarios Tool will count all events unconditionally (subject to the Sampling configuration discussed above). For core events in addition to unconditionally sampling events, the tool offers the option to capture events based on address ranges: If the PC is inside a particular address range. Start counting when PC hits a start address and end collection when the PC reaches a given address. Figure 4.2 Filter Core Events 4.3 Configure Target Parameters As all boards and systems are not configured the same way, the tool allows the user to change the default values of certain important parameters. These values are used in internal calculations of several metrics. The default values represent typical values of a Freescale Development board. Figure 4.3 Configure Target Parameters 32

38 Advanced Options Realtime Data Visualization 4.4 Realtime Data Visualization The Realtime Data Visualization feature provides graphical representations of all event counts as the data is sampled. Data is collected on a best-effort basis and immediately displayed in a Live Graph so that user can see the changes or trends in realtime. This type of visualization is available when collecting a small amount of fixed data, or when collecting data in an on-going or continuous manner. This section explains the following topics: Enabling Realtime Data Visualization Visualizing Data Visualizing Deltas or Absolutes Filtering Graphs Toolbar Combining Graphs Updating the Y-Axis Range Enabling Realtime Data Visualization To enable the Realtime Data Visualization, expand the Realtime Visualization section in the Scenario Configuration. Select the Enable Realtime Data Visualization checkbox. Figure 4.4 Realtime Data Visualization 33

39 Advanced Options Realtime Data Visualization The option Display size configures the samples that are visible at one time. The Display size is set to the default of 300 samples Visualizing Data When the visualization is enabled, launch the session to begin the sampling data. The Realtime view is displayed automatically in the lower right area of the workbench. Each event count is drawn in its own graph. Data is added to the right-side of the graph and moves from right to left as new data is sampled. The X-axis displays the time when the sample was captured. If time cannot be calculated then the sample index is displayed. The Y-axis displays the sample value. Figure 4.5 Realtime DDR Traffic Visualizing Deltas or Absolutes The default delta values are plotted. To visualize absolute values, expand the section Sampling in the Scenario Configuration. Select the Absolute option under the header Sample Values and then launch the session to begin sampling. 34

40 Advanced Options Realtime Data Visualization Figure 4.6 Sampling Values Filtering Graphs The graphs for all default event counts are displayed. Graphs can be filtered using the Display measurements field. Enter the filter text and click the Apply button. Figure 4.7 Filtering Graphs Toolbar The toolbar provides the following actions: Add Annotation Opens a dialog to add a single annotation to the currently selected graph Remove Annotation Opens a dialog to remove a single annotation from the currently selected graph Undo Supports undoing annotations that were previously added with single click. Redo Supports redoing annotations that were previously removed with single click. Save Snapshot to.png file Saves a snapshot of the currently selected graph Figure 4.8 Graph Toolbar 35

41 Advanced Options Realtime Data Visualization Combining Graphs To combine graphs, use Ctrl+Click to select the graphs to be combined. Right-click the graphs and select the option Combine graphs. Figure 4.9 Combine graph To separate the graphs and return them to their original state, right-click the combined graph and select the option Separate graphs Updating the Y-Axis Range The graphs are set to default Automatically scale the Y-Axis option. To set the Y-Axis to a fixed range, right-click a graph and select the option Update Y-Axis Range. 36

42 Advanced Options Realtime Data Visualization Figure 4.10 Update Y-Axis Range Select the option Set Y-Axis to fixed range and then enter the Min and Max value for the Y-Axis range. 37

43 Advanced Options Realtime Data Visualization 38

44 5 Custom Scenarios The Processor Expert QorIQ Scenarios Tool v2.0 provides the ability to analyze a system's Performance Monitor Events. The tool allows the user to select predefined Analysis Configurations called Stock Scnearios. A stock scenario configures events that are to be measured and pre-defined metrics to be calculated on the data that is collected. As users become more familiar with the system that they are measuring, the ability to create their own Scenarios is crucial. Most users desire the ability to create a Custom Scenario in order to minutely narrow or extend their analysis. A Custom Scenario may be created in one of two ways: Modify an existing Stock Scenario to generate a new scenario Create a new Scenario from scratch. This chapter contains the following sections: Modify an Existing Scenario 5.1 Modify an Existing Scenario To modify an existing scenario, the user selects the New Custom Scenario button on the tool bar(also available from the File menu): Figure 5.1 New Custom Scenario Button The wizard will guide the user through the appropriate steps. A New Custom Scenario wizard will appear and that will allow the user to navigate through the existing scenarios. 39

45 Custom Scenarios Modify an Existing Scenario Figure 5.2 Create a new Custom Scenario Page Click Next to select a scenario. Figure 5.3 Selecting an existing Scenario as starting point 40

46 Custom Scenarios Modify an Existing Scenario After selecting the scenario to be edited, click the Finish button. The Custom Scenario editor is displayed to the user. It contains four tabs: Overview Events Metrics Initialization Overview The overview window provides a brief summary of the scenario that the user is creating or editing. It replicates the information that was entered during the creation of the scenario Events This is the main window in the Custom Scenario Editor. It will list all of the device's components that have events available for configuration. Because there can be several hundred of these events, to make it easier to locate an event of interest, this window has a search window where the user can type a search string. In the example below, as the word 'branch' is entered, the tool has displayed all events that include the word 'branch' in their description. Once an event of interest has been located, select it and choose the Add button. The selected event will be added to the list of selected events in the right hand side of the display. The tool will automatically handle the allocation of the event to a given counter and it will manage the available counters as well. As soon as all counters have been assigned, any other events listed will be grayed out. If the user attempts to add an event from the grayed out list, the tool will display an error message indicating that there are no more counters available to assign. 41

47 Custom Scenarios Modify an Existing Scenario Figure 5.4 Events Assignment Metrics The Metrics tab is the place where a user can define (optionally) metrics (mathematical operations) of measured events. If the user has selected a predefined scenario to edit, then this tab will show the metrics that have been defined for a scenario. Name Metric name Expression Metric expression which is a combination of event names and mathematical operands Alias Shortened Name to be displayed in the results The Metrics toolbar can be used to complete the following actions: Add a new Metric Edit an existing Metric that is selected in the table Remove a Metric that is selected in the table 42

48 Custom Scenarios Modify an Existing Scenario Figure 5.5 Custom Scenarios Defining Metrics When the user presses the Add Metric button (the "plus" sign in the tool bar) a dialog box will appear: Figure 5.6 Custom Scenarios Metric Definition From this dialog, the user can specify the Name, Expression, and Qualifier for the Metric using the text fields. The Events button will bring a dialog box that allows the user to select the necessary events for 43

49 Custom Scenarios Modify an Existing Scenario a metric. As metrics are operations on events, the user will also need to choose an appropriate operator using the Operators button. Pressing OK will complete the definition of the metric Initialization In some cases, a user may require advanced target initialization beyond the configuration that enables the event-counter pairs. In this case, the user can click on the Initialization tab and a window is displayed where a python script can be entered directly into a text editor field. Optionally, the user can search the filesystem for previously saved python scripts. Figure 5.7 Scenario Editor Initialization 44

50 6 Scenario Reference This chapter explains how to configure a scenario and different types of available scenarios. This chapter contains the following sections: Scenario Selection and Configuration Available Scenarios 6.1 Scenario Selection and Configuration Table 6.1 lists and describes the Connection toolbar buttons available to work with the configuration settings. These settings are in the Scenarios Section of the Configuration tab. Table 6.1 Configuration Pane Scenarios Toolbar Buttons Option Description Add a stock scenario Click to open the Add <Target Processor> Stock Scenarios dialog box. This option is used to select different stock scenarios. A stock scenario is the standard scenarios available on the tools. Delete a stock scenario Select to delete a stock scenario. Click to open the Add <Target Processor> Stock Scenarios dialog box. The scenario needs to be selected in order for this option to be enabled. 45

51 Scenario Reference Available Scenarios Table 6.1 Configuration Pane Scenarios Toolbar Buttons Option Description Move Scenarios Up To Change the Order or Execution Select to move scenarios up in the order of execution. This option is only available when multiple scenarios have been added. The Scenarios will run in the order that they appear in the Scenarios view. All scenarios are independent of each other. Move Scenarios Down To Change the Order or Execution Select to move scenarios down in the order of execution. This option is only available when multiple scenarios have been added. The Scenarios will run in the order that they appear in the Scenarios view. All scenarios are independent of each other. 6.2 Available Scenarios Scenarios can be selected from the Configuration screen Scenarios section. 46

52 Scenario Reference Available Scenarios Figure 6.1 Selecting Bare Board Stock Scenarios The following table shows a representative list of the type of scenarios available in the tool. Refer to the tool to get an accurate list of scenarios since they vary by device. Table 6.2 Available Scenarios Scenarios Description CPU Utilization - Branch Miss Ratio Utilization - Interrupt Count Utilization - CPU Usage in Supervisor and User Mode Utilization - CPU Usage and IPC Cache - Data Cache Operations Cache - Data L1 Cache Miss Measures Branch misprediction ratio for any reason Counts interrupt occurrences CPU Loading that indicates Supervisor/User Privilege and IPC Measurement Counts percent of total cycles spent in a PMM marked range of code and counts number of instructions Measures Several Data Cache operations Measures Data L1 Cache miss related statistics 47

53 Scenario Reference Available Scenarios Table 6.2 Available Scenarios Scenarios Cache - Backside L2 Cache Data Miss Cache - Backside L2 Cache Instruction Hit ratio MMU - Data MMU TLB, VSP reloads and L2 MMU Misses MMU - Instruction TLB, VSP reloads and MMU misses MMU - Data MMU Miss Cycles MMU - Data MMU Miss with Data side L2 MMU Misses Core Complex - Core Complex Traffic Core Complex Traffic - Cache OPS and cache inhibited Load Store Unit - Data Line Fill Buffer (DLFB) Miss with Threshold Description Counts L2 Backside Cache Misses per L2 Data Cache Access Counts L2 Backside Cache Misses per L2 Instruction Cache Access Measures CPU MMU Misses Instruction TLB, VSP Reloads and MMU Misses Measures Data MMU Miss Cycles Measures Data MMU Miss Cycles Measures Traffic in the Core Complex Measures Cache OPS and cache inhibited accesses in the Core Complex Measure instances when the cycles between load allocation in Data LFB entry0 and writeback exceeds threshold DDR DDR Traffic DDR Traffic with Page Miss and Collision Analysis DDR1 only Traffic with Page Miss DDR Traffic with Command Queue Full DDR Traffic with Command Queue Full and Reorder from DDR CoreNet Platform Cache 1 DDR statistics including read/write cycles and page collision counts DDR statistics including read/write cycles, page collisions counts and page miss analysis DDR1 only statistics including read/write cycles and page collision counts and command queue full counts DDR1 only statistics including read/write cycles and page collision counts and command queue full counts DDR1 only statistics including read/write cycles and page collision counts, command queue full counts and reorder counts. 48

54 Scenario Reference Available Scenarios Table 6.2 Available Scenarios Scenarios Description DPAA QMan QMan_DQ QMan_EQ_DQ_DCP012 QMan_DCPx_eq_dq_cmd_full DPAA SEC deco_idle OceaN nxc_dma1_rw nxc_dma2_rw nxc_dma_desc_req Combination CPU(all, L1, BIU)_CPC(RWO- HM)_DDR(PH,PM) CPU(all,L1_BIU)_CPC1(RWO- HM)_DDR1(PH,PM) cpu_loading_with_pkt_flow SC3900 Events - SC3900 Exceptions Events - SC3900 Branch Prediction Events - SC3900 Debug Events Cycles - SC3900 Cycles High Level Cycles - Stalls Cache - Instruction Channel - SC3900 L1 Pcache Access Sorting Cache - Data Channel - General - SC3900 Data Coherency Counts exceptions occurrence Measures branch prediction events Counts various debug events on the IEU and Reload Counter Measures application cycles and bubbles Measures application stalls Measures L1 instruction cache events Counts data cache invalidation events 49

55 Scenario Reference Available Scenarios 50

56 7 Data Display Reference This chapter explains how data is displayed in different formats. This chapter contains the following sections: Table View Graph View This pane displays the event data that was generated from the scenario tool. There are two ways in which the data can be displayed: In a table (Table View) In a graph (Graph View) Figure 7.1 Table View Data Collection Pane 51

57 Data Display Reference Table View 7.1 Table View The Data collection tab is a multi-tab display. The first tab at the bottom of the window is called Results. The data displayed in this tab is text data that can be scrolled up/down or scrolled side to side to see all of the data. The rows display the number of samples generated and the columns display the number of events generated. There is one event per core generated in each column Data Viewing Options If only certain event data wants to be viewed, columns may be hidden. Even though the columns are hidden in the Results view they will appear in the Graphs view. Also, the hidden columns will appear in the exported.csv file. To hide a column, follow steps below: 1. Right-click the column header, a context menu appears. 2. From the context menu, select Hidden Columns. If more than one column needs to be hidden then you can select the first column, and press the shift key and then select the second column Exporting the Data To export the data that appears in the results window, follow steps below: 1. Right-click the column header; a context menu appears. 2. From the context menu, select Export to CSV. The Export Table as CSV window appears. 3. In the insert name text box, insert name to save file. 4. Select Save. 7.2 Graph View If you select the Graph tab a collection of graphs for the collected data (and associated metrics) is displayed. 52

58 Data Display Reference Graph View Figure 7.2 Graphical View of the Results The Graphs tab displays the results in graphical format. A graph will be generated for each event per core. Right-clicking on any portion of the graph will present a pop-up menu that allows the user to: Restore Graph Defaults Hide/Restore a Graph Chose measurements to display The figure below shows a dialog that will be shown if the user wants to chose which measurements to display: 53

59 Data Display Reference Graph View Figure 7.3 Measurement Chooser The Graph view provides a tool bar that allows the user to manipulate and interact with the graphs. Below is the table with the description of each of the scroll buttons. Table 7.1 Graphics Controls Buttons Description Configure Settings. This allows the graph data to be modified. There is one of these settings per graph. Add annotation Configure annotation Perform Auto Scale will automatically scale up/down the x and y axis. 54

60 Data Display Reference Graph View Exporting Graphical Data The data in the graphs window can be exported into a.csv file. Each graph has to be exported individually. To export a graph into.csv format, follow the below steps: 1. In the graph window, scroll down to the graph that you would like to export. 2. From the toolbar above graph, select the last icon called Save Snapshot to PNG file. The Save As window appears. 3. In the File name text box, insert a name to save the graphical data. 4. Select Save. The Save As window closes. The third tab is called Configuration and is a read-only window. This is the information about the connection method being used to communicate to target hardware Companion Graph Feature The table results page of a performance analysis collection view can optionally show a graph for the event or metric selected in the table. Normally, the table page shows only a table, but by clicking the Companion Graph toolbar option, a graph will appear below the table. The graph and the table are linked such that selections made in one are reflected in the other. Specifically, The graph shows whatever single metric or event you have selected in the table You can highlight an area in the graph and it reduces the table to that range of samples You can select a range of cells in the table and it highlights the corresponding region in the graph You can select a cell in the table and it shows an annotation in the graph You can move the annotation in the graph and the corresponding cell in the table is highlighted 55