As part of configuring the application/module profile, you can specify the application to launch and/or binary module files that you are most interested in. Examples of module file types that you can specify include: executable files and shared library files .
By default, the specified application is the focus of analysis. However, if you are interested in the performance of other modules or applications running on your system, you can add them to the Modules of Interest list.
Specifying Modules of Interest enables some data collectors to enhance the data collection on these modules. Each data collector uses the Modules of Interest differently. See the online help on the particular data collector for specific details.
Modules of interest are useful in these examples:
When your application uses one or more shared libraries, adding the shared libraries as modules of interest focuses the data collection on the launched application and the shared libraries.
When using a script file to launch more than one executable, choosing the executables as modules of interest focuses the data collection on the launched files, instead of the script file.
Setting .so files as modules of interest for call graph profiling is not supported.