Conditionally terminating the profiler

Is there a way to terminate the profiler based on some conditions? I mean specifying a termination point after 1B instructions or 1M cycles? I didn’t find such a way. If that is not present in the current version, I hope that it is considered in a wish list. Don’t know how much that is practical though.

The ncu option “–kill on” can be used to terminate the target application when the requested “–launch-count” was profiled.