Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#181 opreport won't report INST_RETIRED.ANY_P events

closed-fixed
nobody
None
5
2009-03-19
2009-03-05
Jim Blandy
No

I ran oprofile with the following daemonrc:

SESSION_DIR=/var/lib/oprofile
CHOSEN_EVENTS_0=INST_RETIRED.ANY_P:10000:0:1:1
NR_CHOSEN=1
SEPARATE_LIB=0
SEPARATE_KERNEL=0
SEPARATE_THREAD=0
SEPARATE_CPU=0
VMLINUX=none
IMAGE_FILTER=/home/jimb/mc/tm/js/src/obj~/js,/home/jimb/mc/lazy-tm/js/src/obj~/js
CPU_BUF_SIZE=0
CALLGRAPH=0
XENIMAGE=none

I got a /var/lib/oprofile directory with filenames like:

10502576 460 -rw-r--r-- 1 root root 655468 Mar 5 11:02 /var/lib/oprofile/samples/current/{root}/home/jimb/mc/tm/js/src/obj~/shell/js/{dep}/{root}/home/jimb/mc/tm/js/src/obj~/shell/js/INST_RETIRED.ANY_P.10000.0.all.all.all
10503972 460 -rw-r--r-- 1 root root 655468 Mar 5 11:04 /var/lib/oprofile/samples/current/{root}/home/jimb/mc/lazy-tm/js/src/obj~/shell/js/{dep}/{root}/home/jimb/mc/lazy-tm/js/src/obj~/shell/js/INST_RETIRED.ANY_P.10000.0.all.all.all

so it seems the daemon liked it. But opreport doesn't:

$ opreport
opreport error: parse_event_spec(): bad event specification: INST_RETIRED.ANY_P.10000.0.all.all.all
$

Discussion

  • Jim Blandy
    Jim Blandy
    2009-03-05

    For whatever it's worth, that's the event name as listed by 'opcontrol --list-events':

    oprofile: available events for CPU type "Core 2"
    ...
    INST_RETIRED.ANY_P: (counter: all)
    number of instructions retired (min count: 6000)

    Using INST_RETIRED instead works, and may actually have been what I wanted in the first place, but still --- yuck.

     
  • Jim, this invalid event name was fixed in events/i386/core_2/events in oprofile cvs back in Sept 2006. Please download oprofile 0.9.4 and test that out. And I would also ask if you would verify that the other bugs you opened are still problems in this latest release. If not, please close them; but if they are still problems, please add a comment to that effect.

    By the way, you'll often get a quicker response to problems if you post questions to the oprofile-list first. Lots of community members out there who are willing to help, but only a couple of us maintainer types who actually work on bugs.

    Thanks.

     
  • Jim Blandy
    Jim Blandy
    2009-03-19

    • status: open --> open-fixed
     
  • Jim Blandy
    Jim Blandy
    2009-03-19

    Seems to be fixed in the latest sources.

     
  • Jim Blandy
    Jim Blandy
    2009-03-19

    Fixed in current sources.

     
  • Jim Blandy
    Jim Blandy
    2009-03-19

    • status: open-fixed --> closed-fixed