My app has some areas that show a very high performance impact from 64k aliasing in VTune. After studying the problem I've put together some test applications to try to understand why I would be experiencing 64k aliasing. The code below shows a 64k aliasing performance impact of about 80, which is 40x the recommended top end. However, it works only in 2 2K L1 cache regions that are seperated by exactly 8MB + 32K, so there should be no possibility of any 64k aliasing events at all. Can you explain why this is throwing so many events??