Closed GoogleCodeExporter closed 9 years ago
As it turned out this is an error in the Intel documentation.
It is fixed now and works but needs more testing.
Additionally it should b enforced that only one instance per socket
measures these events.
Original comment by jan.trei...@gmail.com
on 8 Feb 2010 at 4:13
This was a documentation error in the Intel Manual.
Works in new Perfmon modules.
Also a socket lock was added to allow only one thread to turn the
Uncore events on and off.
Original comment by jan.trei...@gmail.com
on 27 Apr 2010 at 8:29
Original issue reported on code.google.com by
jan.trei...@gmail.com
on 28 Sep 2009 at 8:25