Texas Instruments TMS320C6 Series, Руководство пользователя

Страница: 201 / 304

Viewing Profile Data
10-19 Profiling Code Execution
Data accuracy
During a profiling session, the debugger sets many internal breakpoints and
issues a series of RUNB commands. As a result, the processor is momentarily
halted when entering and exiting profiling areas. This stopping and starting
can affect the cycle count information (due to pipeline flushing and the
mechanics of software breakpoints) so that it varies from session to session.
This method of profiling is referred to as
intrusive profiling.
Treat the data as
relative, not absolute. The percentages and histograms are
relevant only to the cycle count from the starting point to the stopping
point—not to overall performance. Even though the cycle counts may change
if you profiled the same area twice, the relationship of that area to other profiled
areas should not change.
Sorting profile data
By default, the data displayed in the PROFILE window is sorted according to
the memory addresses of the displayed areas. The area with the least signifi-
cant address is listed first, followed by the area with the next least significant
address, etc. When you view fields individually, the data is automatically sorted
from highest cycle count to lowest (instead of by address).
You can sort the data on any of the data fields by using the View
→
Sort menu.
For example, to sort all the data on the basis of the values of the Inclusive field,
use View
→
Sort
→
Inclusive; the area with the highest Count field will display
first, and the area with the lowest Count field will display last. This applies even
when you are viewing individual fields.
Viewing different profile areas
By default, all marked areas are listed in the PROFILE window. You can modify
the window to display selected areas. To do this, use the selections on the
View
→
Filter pulldown menu; these selections are summarized in Table 10–7.