About this book
Using this book
This book is organized into the following chapters:
- Chapter 1 Target setup
ARM Streamline Performance Analyzer is a system-wide visualizer and profiler for targets running ARM Linux or Android native applications and libraries. To get started using it, you must set up your target, then build and configure
gator, the mechanism that Streamline uses to communicate with your target.
- Chapter 2 The Streamline Data view
The Streamline Data view enables you to set target connection settings, start and stop capture sessions, and create new Streamline Analysis Reports from stored capture sessions.
- Chapter 3 Capture options
The Capture Options dialog box enables you to change capture session settings such as duration, sample rate, and buffer size.
- Chapter 4 Counter configuration
ARM Streamline provides a counter configuration dialog box that enables you to modify what data is collected at runtime.
- Chapter 5 The Live view
The Live view provides capture data in real-time, updating bar chart charts as long as the capture session is active.
- Chapter 6 The Timeline view
The Timeline view charts data over the course of the execution and lists every process invoked during the capture session.
- Chapter 7 The Table Views: Call Paths, Functions, and Stack
Although the information contained in the Call Paths, Functions, and Stack views differ, their basic functionality is similar. Each one is a table report, with rows for each function and columns for each statistical category.
- Chapter 8 The Code view
Of all of the views available in ARM Streamline, the Code view provides the highest level of detail. It breaks statistics down by individual line of code and disassembly instruction.
- Chapter 9 The Call Graph view
The Call Graph view displays your code as a visual call hierarchy and color codes functions to highlights bottlenecks.
- Chapter 10 Streamline Annotate
Use the Annotate feature to customize the data in the Streamline Analysis Reports. In addition to the color-coded overlays it adds to the Timeline view, the Annotate feature records each message generated by the inserted Annotate code and lists it in the Log view.
- Chapter 11 The Log view
The Log view lists every message generated by the
ANNOTATE_VISUALstatements in your code along with information related to the message.
- Chapter 12 The Energy Probe
The Energy Probe is a compact probe designed for application and system software developers to measure any combination of power, voltage, and current in up to three channels. The combination of ARM Streamline and Energy Probe enables the visualization of power metrics against the software behavior of your target hardware. It provides a better understanding of the static and dynamic behavior of your target system for the purposes of debugging, profiling, and analysis.
- Chapter 13 Advanced customizations
ARM Streamline enables you to perform tasks such as creating a report and examining the data available in the report. It enables you to perform these tasks without going to the command line or modifying XML files. However, if you want to customize the data that ARM Streamline collects and change how it is presented to you, or you want to capture data and store it on your target, advanced customizations are required.
- Chapter 14 Troubleshooting common Streamline issues
These topics describe how to troubleshoot common Streamline issues:
- Chapter 15 Using Streamline on the command line
Much of the functionality of Streamline is available on the command line using the
streamlinecommand. You can initiate capture sessions, produce Analysis Reports from existing Captures, and output report data, all without opening the user interface.
The ARM Glossary is a list of terms used in ARM documentation, together with definitions for those terms. The ARM Glossary does not contain terms that are industry standard unless the ARM meaning differs from the generally accepted meaning.
See the ARM Glossary for more information.
- Introduces special terminology, denotes cross-references, and citations.
- Highlights interface elements, such as menu names. Denotes signal names. Also used for terms in descriptive lists, where appropriate.
- Denotes text that you can enter at the keyboard, such as commands, file and program names, and source code.
- Denotes a permitted abbreviation for a command or option. You can enter the underlined text instead of the full command or option name.
- Denotes arguments to monospace text where the argument is to be replaced by a specific value.
- Denotes language keywords when used outside example code.
- Encloses replaceable terms for assembler syntax where they appear in code or code fragments. For example:
MRC p15, 0 <Rd>, <CRn>, <CRm>, <Opcode_2>
- SMALL CAPITALS
- Used in body text for a few terms that have specific technical meanings, that are defined in the ARM glossary. For example, IMPLEMENTATION DEFINED, IMPLEMENTATION SPECIFIC, UNKNOWN, and UNPREDICTABLE.