When running the autorange_profiling example, I see that it collects data over two ranges, one for each of the kernel launches that happen in the example. The range descriptions are “0” and “1”. Is there any way, when using autorange profiling, to get more information about what code the range represents than just a number indicating the order in which the kernels were observed? For example, is there a way to programmatically determine that the range with description “0” corresponds to the kernel named VecAdd and that “1” corresponds to VecSub, or the line numbers of the kernel launches, or things of that nature?
Also, the Perfworks Metrics API has documentation in the Usage section of the CUPTI documentation, but there is no corresponding documentation on its functions or data structures in the Modules or Data Structures sections of the CUPTI documentation. Is there more documentation on the Perfworks Metrics API available somewhere?