OPCONTROL(1)                                                      OPCONTROL(1)


       opcontrol - control OProfile profiling


       opcontrol [ options ]


       opcontrol can be used to start profiling, end a profiling session, dump
       profile data, and set up the profiling parameters.


       --help Show help message.

              Show version.

              Shows the monitorable events.

       --init Load the OProfile module  if  required  and  make  the  OProfile
              driver interface available.

              Followed  by  list  options  for profiling setup. Store setup in
              ~root/.oprofile/daemonrc. Optional.

              Start the oprofile daemon without starting profiling. Not avail-
              able in 2.2/2.4 kernels.

              Start  data collection with either arguments provided by --setup
              of information saved in ~root/.oprofile/daemonrc.

       --dump Force a flush of the collected profiling data to the daemon.

       --stop Stop data collection. Not available in 2.2/2.4 kernels.

              Stop data collection and kill the daemon.

              Clear out data from current session, but leaves saved  sessions.

              Save data from current session to sessionname.

              Shut down daemon. Unload the oprofile module and oprofilefs.

              Set kernel buffer to num samples.

              Set kernel per cpu buffer to num samples (2.6 only). If you pro-
              file at high rate it can help to increase this if the  log  file
              show excessive count of sample lost cpu buffer overflow.

              Add  an  event to measure for the hardware performance counters,
              or "default" for the default event. The event  is  of  the  form
              "CPU_CLK_UNHALTED:30000:0:1:1"  where  the  numeric  values  are
              count, unit mask, kernel-space  counting,  user-space  counting,

              Separate  samples  based on the given separator. ’lib’ separates
              dynamically linked library  samples  per  application.  ’kernel’
              separates  kernel  and  kernel  module  samples per application;
              ’kernel’ implies ’library’. ’thread’ gives separation  for  each
              thread  and  task.   ’cpu’ separates for each CPU. ’all’ implies
              all of the above options and ’none’ turns off separation.

              Enable callgraph sample collection with a maximum depth.  Use  0
              to  disable  callgraph  profiling. This option is currently only
              usable on x86,  using  a  2.6+  kernel  with  callgraph  support

              Only  profile  the given absolute paths to binaries, or "all" to
              profile everything (the default).

              vmlinux kernel image.

              Use this when you don’t have a  kernel  vmlinux  file,  and  you
              don’t want to profile the kernel.

              Be verbose in the daemon log. This has a high overhead.

              Set kernel range vma address in hexadecimal.


       No special environment variables are recognised by opreport.


              Configuration file for opcontrol

              The location of the generated sample files.


       This man page is current for oprofile-0.8.2.


       /usr/share/doc/oprofile/, oprofile(1)

4th Berkeley Distribution      Wed 13 April 2005                  OPCONTROL(1)

Man(1) output converted with man2html