Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 234732 - Core 2 events have wrong names
Summary: Core 2 events have wrong names
Alias: None
Product: Fedora
Classification: Fedora
Component: oprofile
Version: rawhide
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: William Cohen
QA Contact:
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2007-04-01 02:30 UTC by Ulrich Drepper
Modified: 2008-05-07 01:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-05-07 01:23:36 UTC

Attachments (Terms of Use)

Description Ulrich Drepper 2007-04-01 02:30:23 UTC
Description of problem:
Some of the events for Core 2 processors (and maybe other variants) have wrong
names.  The architecture manual is the ultimate reference and deviating means
causing problems.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.opcontrol -e SSE_PRE_MISS:500:0:0:1
Actual results:
No such event "SSE_PRE_MISS"

Expected results:
Nothing.  Should work fine.


Additional info:
I'll commit the report right away and might add to it if I find more problems.

Comment 1 Ulrich Drepper 2007-04-01 04:55:59 UTC
Next Typo:

STORE_BLOCK: (counter: all)
        0x08: NOOP      A store is blocked due to a conflict with an external or
 internal snoop.

This is supposed to be "SNOOP" and not "NOOP".

Comment 2 Ulrich Drepper 2007-04-01 05:29:52 UTC

These all should be BUS_TRANS_* (note the extra 'S').

Comment 3 Geoff Gustafson 2007-09-14 19:08:43 UTC
Checking w/ Intel on updating the documentation.

Comment 4 William Cohen 2007-10-05 15:53:40 UTC
Any progress checking with Intel people about the canonical names for the core2

Comment 5 Geoff Gustafson 2007-10-05 16:27:59 UTC
No response to my email, so I sent another one.

Comment 6 Bug Zapper 2008-04-03 23:52:49 UTC
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:

We will be following the process here: to ensure this
doesn't happen again.

Comment 7 Bug Zapper 2008-05-07 01:23:34 UTC
This bug has been in NEEDINFO for more than 30 days since feedback was
first requested. As a result we are closing it.

If you can reproduce this bug in the future against a maintained Fedora
version please feel free to reopen it against that version.

The process we're following is outlined here:

Note You need to log in before you can comment on or make changes to this bug.