From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.6) Gecko/20040116 Description of problem: On Athlon64: opcontrol --list-events lists the events for the Athlon processor but not for the Athlon64. Version-Release number of selected component (if applicable): 0.7cvs How reproducible: Always Steps to Reproduce: 1.opcontrol --list-events 2. 3. Actual Results: The list of events for the Athlon. Expected Results: The list of events for the Athlon64 (as seen on the oprofile web site: http://oprofile.sourceforge.net/docs/amd-hammer-events.php3) Additional info:
The events for the AMD64 are a pure superset of the Athlon events. One can still get measurements even with the processor being misidentified as a regular Athlon. However oprofile will not have access to the AMD64 specific events such as the ones related to the hypertransport channels. This problem is due to the kernel misidenting the processor. I have verified this problem has been fixed in the kernel in Rawhide (FC2-test3).
I'm interested in FPU-related events. Where is the misidentification problem? If this helps, the kernel correctly prints in /proc/cpuinfo: model name : AMD Athlon(tm) 64 Processor 3200+
The oprofile kernel driver has its own cpu identification code; it is separate from the /proc/cpuinfo. In the case of the x86_64 it is going to be in arch/i386/oprofile/nmi_int.c of the kernel.
The oprofile driver provide the cpu identification information in /dev/oprofile/cpu_type.