all with the
The samples can be attributed to processes, or to processes and modules, or not attributed. For example:
| • |
| Measure for system activity, and attribute samples to |
| processes and modules within those processes whenever |
| possible. Samples will be attributed to functions within |
| those modules, and assembly and source listings in the |
| Function Details sections are available. |
| If you use the |
| |
| The |
| be specified as |
| • |
| Measure for system activity, and attribute samples to |
| processes (but not to modules within those processes) |
| whenever possible. No Function Details sections are |
| available, because attribution of samples is not done |
| on specific modules. |
| • |
| Measure for system activity, but do no attribution to |
| individual processes running on the system. The only |
| sample attribution possible is to kernel modules. |
| Therefore, this qualifier makes sense only if the privilege |
| level is kernel or all. |
| When the scope is system, the |
| program and program_args should not be provided. |
pset | The subject of measurement is user and kernel activity on |
pset_id[:pset_id:...] | all CPUs belonging to the specified processor sets (psets). |
| (You can change the privilege level using the |
| |
| pset 0:1 measures all CPUs belonging to psets 0 and 1. |
| You can use the psrset |
| assignment for all processor sets in the system. |
For details on how to use
Using
When the scope is system, you can specify whether you want the samples to be attributed to the processes they belong to, or to the processes and the modules of those processes, or not attributed. Using
With
70 HP Caliper Options