Menu
▾
▴
[oprof-cvs] CVS: oprofile/doc Makefile.in,1.13,1.14 oprofile.1.in,1.24,1.25 oprofile.sgml,1.71,1.72
|
From: Philippe E. <ph...@us...> - 2002-01-23 21:16:58
|
Update of /cvsroot/oprofile/oprofile/doc In directory usw-pr-cvs1:/tmp/cvs-serv3503/oprofile/doc Modified Files: Makefile.in oprofile.1.in oprofile.sgml Log Message: doc / pp: op_merge utility Index: Makefile.in =================================================================== RCS file: /cvsroot/oprofile/oprofile/doc/Makefile.in,v retrieving revision 1.13 retrieving revision 1.14 diff -u -d -r1.13 -r1.14 --- Makefile.in 2002/01/22 05:10:34 1.13 +++ Makefile.in 2002/01/23 21:16:54 1.14 @@ -10,7 +10,7 @@ MKDIR=mkdir MKDIR_P=mkdir -p DB2HTML=db2html -LINK_LIST=oprofiled.1 op_start.1 op_stop.1 op_help.1 oprofpp.1 op_time.1 op_to_source.1 +LINK_LIST=oprofiled.1 op_start.1 op_stop.1 op_help.1 oprofpp.1 op_time.1 op_to_source.1 op_merge.1 .PHONY: all clean install uninstall Index: oprofile.1.in =================================================================== RCS file: /cvsroot/oprofile/oprofile/doc/oprofile.1.in,v retrieving revision 1.24 retrieving revision 1.25 diff -u -d -r1.24 -r1.25 --- oprofile.1.in 2002/01/22 05:10:34 1.24 +++ oprofile.1.in 2002/01/23 21:16:54 1.25 @@ -27,6 +27,12 @@ ] [ samples-files-directory ] .br +.B op_merge +[ +.I options +] +[ samples-filenames or binary-filename] +.br .B op_help [ event-name ] .br @@ -291,6 +297,17 @@ sort output by increasing count of samples rather by decreasing count of samples .TP .br +.B op_merge options +.br +.TP +.BI "--use-counter " counter_nr ", -c "counter_nr +which counter to use for selecting filenames purposes +.TP +.br +.BI "--base-dir " directory_name ", -b "directory_name +where are located samples files. Default is /var/opd/samples +.TP +.br .B oprof_convert filename [filenames] The oprof_convert utility is only needed when upgrading the profiler version. Further details can be found in the HTML documentation. @@ -327,6 +344,9 @@ .PP .B op_time utility can be usefull to get an overall of all profiled applications. +.PP +.B op_merge +utility can be usefull to merge samples files which belongs to the same binary image .PP .SH ENVIRONMENT No environment variables are recognised by oprofile. Index: oprofile.sgml =================================================================== RCS file: /cvsroot/oprofile/oprofile/doc/oprofile.sgml,v retrieving revision 1.71 retrieving revision 1.72 diff -u -d -r1.71 -r1.72 --- oprofile.sgml 2002/01/21 02:47:27 1.71 +++ oprofile.sgml 2002/01/23 21:16:54 1.72 @@ -274,9 +274,20 @@ <listitem><para> This utility can be used to produce annotated source, assembly or mixed source/assembly. Source level annotation is available only if the application was compiled with - debugging symbols. See <xref linkend="op-to-source">. + debugging symbols. See <xref linkend="op-to-source">. </para></listitem> </varlistentry> + +<!-- FIXME: how to get a link only for the word op_merge and so on remove + the ugly See the section called .... in Chapter X --> +<varlistentry> + <term><filename>op_merge</filename></term> + <listitem><para> + This utility is useful to merge samples files which belongs to the same application + especially when you profile with separating samples for shared libs. See <xref linkend="op-merge">. + </para></listitem> +</varlistentry> + </variablelist> </chapter> @@ -1057,6 +1068,31 @@ <listitem><para> Comma-separated list of symbols to ignore. This can be useful to ignore the leading contributors to the sample histogram, as the percentage values are re-calculated. + </para></listitem> + </varlistentry> +</variablelist> +</para> +</sect1> + +<sect1 id="op-merge"> +<title><command>op_merge</command>: merging samples files</title> +<para> +<command>op_merge</command> is used to merge samples wich belongs to the same binary image. Its main purpose +is to merge samples files created by profiling with —separate-samples. So you can create one samples +file containing all samples for a shared libs: +<command>op_merge</command><filename>/usr/lib/ld-2.1.2.so</filename> will create a samples file named +<filename>}usr}lib}ld-2.1.2.so</filename> ready to use with <command>oprofpp</command> or other post-profiling tools. +Additionnaly you can merge a subset of samples files inside one sample file by specifying explicitly the samples files name to merge. +This allows to use post-profile tools on shared libs for a subset of applications. +</para> +<para> +The options allowed are : +<variablelist> + <varlistentry> + <term><option>—use-counter</option> nr</term> + <term><option>-c</option></term> + <listitem><para> + use counter nr to select the appropriate samples files </para></listitem> </varlistentry> </variablelist> |