•
To make duration measurements, set up the trace command to store only the entry
and exit points of the module of interest. For example:
trace after <symbol_entry> or <symbol_exit> only
symbol_entry
or symbol_exit counting time
or
trace after <module_name> start or module_name end only
module_name
start or module_name end counting time
Since the trigger state is always stored, you should trigger on the entry or exit
points.
<symbol_entry> and <symbol_exit> are symbols from the user program.
<module_name> is the name of a C function or Pascal procedure (and is listed
as a procedure symbol in the global symbol display).
Step 2. Initialize the performance measurement
After you set up the trace command, you must tell the SPMT the address ranges on
which you wish to make activity measurements or the time ranges to be used in the
duration measurement. This is done by initializing the performance measurement,
which can be accomplished in various ways.
•
To use the default configuration, enter the following command with no options:
performance_measurement_initialize
This specifies an activity measurement. If a valid symbolic database has been
loaded, the addresses of all global procedures and static symbols will be used.
Otherwise, a default set of ranges that cover the entire processor address range
will be used.
Chapter 7: Making Software Performance Measurements
To use the Software Performance Measurement Tool
289
Summary of Contents for 64783A
Page 30: ...xxx ...
Page 31: ...Part 1 Quick Start Guide 1 ...
Page 33: ...1 Getting Started 3 ...
Page 70: ...40 ...
Page 75: ...Part 2 Using The Emulator 45 ...
Page 140: ...110 ...
Page 141: ...4 Using the Emulator How to control the processor and view system resources 111 ...
Page 227: ...5 Using the Emulation Bus Analyzer How to record program execution in real time 197 ...
Page 290: ...260 ...
Page 331: ...8 Configuring the Emulator 301 ...
Page 382: ...352 ...
Page 383: ...9 Solving Problems What to do when the emulator doesn t behave as expected 353 ...
Page 397: ...Part 3 Reference 367 ...
Page 399: ...10 Using Memory Management Understanding logical and physical emulation and analysis 369 ...
Page 429: ...11 Emulator Commands The command syntax reference for the emulator softkey interface 399 ...
Page 443: ...copy Chapter 11 Emulator Commands copy 413 ...
Page 451: ...display Chapter 11 Emulator Commands display 421 ...
Page 457: ...DISPLAY MEMORY Chapter 11 Emulator Commands DISPLAY MEMORY 427 ...
Page 461: ...DISPLAY MMU Chapter 11 Emulator Commands DISPLAY MMU 431 ...
Page 464: ...DISPLAY TRACE Chapter 11 Emulator Commands DISPLAY TRACE 434 ...
Page 480: ...modify Chapter 11 Emulator Commands modify 450 ...
Page 501: ...set Chapter 11 Emulator Commands set 471 ...
Page 514: ... SYMB Chapter 11 Emulator Commands SYMB 484 ...
Page 582: ...552 ...
Page 583: ...13 Setting X Resources 553 ...
Page 598: ...568 ...
Page 606: ...576 ...
Page 613: ...16 Specifications and Characteristics 583 ...
Page 627: ...Part 4 Concept Guide 597 ...
Page 629: ...17 X Resources and the Graphical User Interface 599 ...
Page 639: ...Part 5 Installation and Service Guide 609 ...
Page 697: ...19 Installation and Service 667 ...
Page 746: ...Chapter 19 Installation and Service Verifying the Installation 716 ...
Page 755: ...20 Installing Updating Emulator Firmware 725 ...
Page 762: ...732 ...
Page 778: ...748 ...
Page 810: ...X server 554 604 X Window System 54 Index 780 ...