Table of Contents
Advertisement
6.2.1
Charts specific to Mali targets
6.2.2
See also
ARM DUI 0482K
ID120712
Core
The total number of instructions executed by each core.
Cache
The number of cache coherency hits and misses. A cache coherency miss occurs
every time a processor tries to read from or write to the cache when it is in
incoherent state. This is more common in SMP systems where multiple
processors share resources. A coherency hit occurs when a processor reads from
or writes to a cache that is in a valid state.
Interrupts
Maps the amount of both soft IRQs and standard, hardware IRQs. Soft IRQs are
similar to IRQs, but are handled in software. Soft IRQs are usually delivered at a
time that is relatively convenient for the kernel code.
Disk IO
Measures the number of times the core triggered reads and writes to disk.
Memory
Charts the available system memory over the time of the execution.
If you are using a target with more than one core, some graphs in the Timeline view have a
disclosure control. Use this to break each graph into multiple sections, one for each core in your
system.
If you have built
gator.ko
the following charts are added to the default set of Timeline view charts:
•
GPU Vertex chart - Streamline reports whether the status of the Mali-400 vertex processor
is idle or active. The load on the vertex processor is proportional to the number of vertices
and the complexity of the shader used to transform their coordinates.
•
GPU Fragment chart - Streamline reports whether the status of the Mali-400 fragment
processor is idle or active. The load on the fragment processor is proportional to the
number of pixels to be rendered and the complexity of the shader used to determine the
final pixel color. Pixels rendered include on and off screen pixels and the additional pixels
required for super sampling.
If you have built gator.ko to support Mali and have run a capture session on a Mali-T6xx target,
Streamline includes the following MaliT-6xx-specific chart types:
•
GPU Job Slot 0 - Streamline reports whether Job Slot 0 is occupied or idle. Job Slot 0
activity generally corresponds to fragment shader work, though this not excelusively the
case.
•
GPU Job Slot 1 - Reports whether Job Slot 1 is occupied or idle. Job Slot 1 activity
generally, but not exclusively, corresponds to vertex shader work, though this not
excelusively the case.
•
GPU Job Slot 2 - Reports whether Job Slots 2 is occupied or idle. Job Slot 2 activity
generally corresponds to GPGPU compute work.
Please refer to the Mali documentation for more details on the GPU Job Slots.
Tasks
•
Customize reports using Annotate on page 10-2
•
Creating custom performance counters on page
Reference
•
Filtering data and other Timeline view controls on page 6-19
Copyright © 2010-2012 ARM. All rights reserved.
Non-Confidential
to support Mali and have run a capture session on a Mali-400 target,
The Timeline View
11-4.
6-11
Advertisement
Table of Contents
