the separate functionality, the names and paths of these sample files are changed to
reflect where the samples were from. This can include thread IDs, the binary file path, the
event type used, and more.
After this final step from interrupt to disk file, the data is now persistent (that is, changes
in the running of the system do not invalidate stored data). This enables the post-profiling
tools to run on this data at any time (assuming the original binary files are still available
and unchanged).
31.2.5 Post Profiling Tools
The collected data must be presented to the user in a useful form. This is the job of the
post-profiling tools. In general, they collate a subset of the available sample files, load
and process each one correlated against the relevant binary file, and produce user
readable information.
31.3 Requirements
OProfile has the following requirements.
• Add Oprofile support with Cortex-A8 Event Monitor
31.3.1 Source Code Structure
Oprofile platform-specific source files are available in the directory:
<ltib_dir>/rpm/BUILD/linux/arch/arm/oprofile/
Table 31-1. OProfile Source Files
File
Description
op_arm_model.h
Header File with the register and bit definitions
common.c
Source file with the implementation required for all platforms
The generic kernel driver for Oprofile is located under <ltib_dir>/rpm/BUILD/linux/
drivers/oprofile/
31.3.2 Menu Configuration Options
The following Linux kernel configurations are provided for this module.
Requirements
i.MX 6SoloLite Linux Reference Manual, Rev. L3.0.35_4.1.0, 09/2013
196
Freescale Semiconductor, Inc.
