8.3.1. Miscellaneous control of profiling

There is a clear requirement for the user code to be able to control the profiler dynamically at run time. This is normally used for (at least) the purposes of

• Enabling and disabling profiling depending on the state of the calculation.
• Flushing trace buffers at non-critical points in the calculation
• Adding user events to a trace file.

MPI_PCONTROL(level, ...)
[ IN level] Profiling level
int MPI_Pcontrol(const int level, ...)
MPI_PCONTROL(level)
INTEGER LEVEL, ...

MPI libraries themselves make no use of this routine, and simply return immediately to the user code. However the presence of calls to this routine allows a profiling package to be explicitly called by the user.

Since MPI has no control of the implementation of the profiling code, we are unable to specify precisely the semantics which will be provided by calls to MPI_PCONTROL. This vagueness extends to the number of arguments to the function, and their datatypes.

However to provide some level of portability of user codes to different profiling libraries, we request the following meanings for certain values of level.

• level==0 Profiling is disabled.
• level==1 Profiling is enabled at a normal default level of detail.
• level==2 Profile buffers are flushed. (This may be a no-op in some profilers).
• All other values of level have profile library defined effects and additional arguments.

The provision of MPI_PCONTROL as a no-op in the standard MPI library allows them to modify their source code to obtain more detailed profiling information, but still be able to link exactly the same code against the standard MPI library.