by ayazakram_89 » Fri Aug 28, 2015 1:26 pm
Hi, I am interested in both. To accomplish that task, I am using attach3 test case in papi source rep. I run the benchmark as child process and from my parent process I keep on reading child's counters to know when particular number of instructions have been executed (starting point of interval of interest) and then I keep track of cycles count until executed instructions number reach close to the end point of interval of interest. Do you think, this is the right solution or is there a better one ?