Skip to Main Content

DevOps, CI/CD and Automation

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

hardware profiling (cache miss counters) not working

807575Jul 23 2009 — edited Jul 26 2009
Dear all,

While doing some hardware profiling (cache miss counters), i am facing following error.

here is the error
$ collect -h L2_dmiss_ld/1,10003
HW counter profiling is not supported on this system: library /usr/local/lib64/libperfctr.so could not be opened
Contents of /usr/local/lib
lib]$ ls
libpapi.a  libpapi.so  libpapi.so.3  libpapi.so.3.6.2  libperfctr.a  libperfctr.so  libperfctr.so.6  libperfctr.so.6.2.6.35  libpfm.a  libpfm.so  libpfm.so.3  libpfm.so.3.5.0
I have installed Sun Studio 12 Update 1 version for Linux
my system architecture is
]$ collect
Path to `/usr/java/bin/java' (set from System Default) does not point to a JVM executable
NOTE: Linux-64-bit, 32 CPUs, CentOS_5.2 system "mi02" is supported by the Performance tools.
 usage:  collect <args> target <target-args>
        Sun Analyzer 7.7 Linux_i386 2009/06/03 [64-bit]
  -p <interval> specify clock-profiling
        clock profiling interval range on this system is from
        10.000 to 1000.000 millisec.; resolution is 10.000 millisec.
  -h <ctr_def>...[,<ctr_n_def>] specify HW counter profiling
        note: HW counter profiling is not supported on this system
  -s <threshold>        specify synchronization wait tracing
  -r <option>   specify thread analyzer experiment; see man page
  -H {on|off}   specify heap tracing
  -M {version|off}      specify an MPI experiment
        Supported MPI versions: CT8.2, CT8.1, CT8, CT7, CT7.1, OPENMPI, MPICH2, MVAPICH2
  -m {on|off}   specify MPI tracing
  -j {on|off|path}      specify Java profiling
  -J <java-args>        specify arguments to Java for Java profiling
  -t <duration> specify time over which to record data
  -x    specify leaving the target waiting for a debugger attach
  -n    dry run -- don't run target or collect performance data
  -y <signal>[,r]       specify delayed initialization and pause/resume signal
        When set, the target starts in paused mode;
          if the optional r is provided, it starts in resumed mode
  -F {on|off|all|=<regex>}      specify following descendant processes
  -A {on|off|copy}      specify archiving of load-objects; default is on
  -S <interval> specify periodic sampling interval (secs.)
  -L <size>     specify experiment size limit (MB.)
  -l <signal>   specify signal for samples
  -o <expt>     specify experiment name
  -d <directory>        specify experiment directory
  -g <groupname>        specify experiment group
  -O <file>     redirect all of collect's output to file
  -v    print expanded log of processing
  -C <label>    specify comment label (up to 10 may appear)
  -R    show the README file and exit
  -V    print version number and exit

 Default experiment:
        expt_name = test.1.er
        clock profiling enabled, 10.000 millisec.
        descendant processes will not be followed
        periodic sampling, 1 secs.
        experiment size limit 2000 MB.
        experiment archiving: on
        data descriptor: "p:10000;S:1;L:2000;A:1;"
                host: `m02', cpuver = -1, ncpus = 32, clock frequency 1200 MHz.
                memory:  16518000 pages @ 4096 bytes = 64523 MB.

 See the collect.1 man page for more information
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Aug 23 2009
Added on Jul 23 2009
1 comment
215 views