Yes this is a known issue with our profiling library, but it is actually a driver issue. I will do some additional testing and will try to revisit this issue with the driver engineers. I will also double check to make sure there is a KB article about it and will update the KB if any additional information becomes available.
hello Peter, thanks!
We revisited the issue and discovered that it was indeed a bug in GPUPerfAPI. The issue has been resolved and we have made GPUPerfAPI 2.8 publicly available.
Please find the new version available at: http://developer.amd.com/gpu/GPUPerfAPI/Pages/default.aspx
Thank you for reporting the issue and we welcome any additional feedback that you have!