[prev in list] [next in list] [prev in thread] [next in thread] 

List:       oprofile-commits
Subject:    [oprof-cvs] CVS: oprofile/doc opcontrol.1.in,1.15,1.16 oprofile.1.in,1.75,1.76 oprofile.xml,1.120,1.
From:       John Levon <movement () users ! sourceforge ! net>
Date:       2004-07-06 21:32:28
Message-ID: E1BhxYC-0001X1-Bc () sc8-pr-cvs1 ! sourceforge ! net
[Download RAW message or body]

Update of /cvsroot/oprofile/oprofile/doc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv5519/doc

Modified Files:
	opcontrol.1.in oprofile.1.in oprofile.xml 
Log Message:
remove sample-file:/binary: (praise the Lord). Allow either "lib" or
"library" for separate/merge options.



Index: opcontrol.1.in
===================================================================
RCS file: /cvsroot/oprofile/oprofile/doc/opcontrol.1.in,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -p -d -r1.15 -r1.16
--- opcontrol.1.in	27 Jan 2004 22:30:08 -0000	1.15
+++ opcontrol.1.in	6 Jul 2004 21:32:25 -0000	1.16
@@ -89,8 +89,8 @@ count, unit mask, kernel-space counting,
 respectively.
 .br
 .TP
-.BI "--separate="[none,library,kernel,thread,cpu,all]
-Separate samples based on the given separator. 'library' separates
+.BI "--separate="[none,lib,kernel,thread,cpu,all]
+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

Index: oprofile.1.in
===================================================================
RCS file: /cvsroot/oprofile/oprofile/doc/oprofile.1.in,v
retrieving revision 1.75
retrieving revision 1.76
diff -u -p -d -r1.75 -r1.76
--- oprofile.1.in	6 Jul 2004 20:45:58 -0000	1.75
+++ oprofile.1.in	6 Jul 2004 21:32:25 -0000	1.76
@@ -140,16 +140,6 @@ libraries, all threads in a process shar
 have different thread IDs. You can use this option in combination with
 tgid: to restrict the results to particular threads within a process.
 This is only useful when using per-process profile separation.
-.br
-.TP
-.BI "binary:"file
-Give results only for the given file. This can only be used with
-sample-file:.
-.br
-.TP
-.BI "sample-file:"sample file
-Give results only for the given sample file. This can only be used with
-binary:.
 
 .SH ENVIRONMENT
 No special environment variables are recognised by oprofile.

Index: oprofile.xml
===================================================================
RCS file: /cvsroot/oprofile/oprofile/doc/oprofile.xml,v
retrieving revision 1.120
retrieving revision 1.121
diff -u -p -d -r1.120 -r1.121
--- oprofile.xml	6 Jul 2004 20:45:58 -0000	1.120
+++ oprofile.xml	6 Jul 2004 21:32:25 -0000	1.121
@@ -577,7 +577,7 @@ is required. These settings are stored i
 		</para></listitem>
 	</varlistentry>
 	<varlistentry>
-		<term><option>--separate=</option>[none,library,kernel,thread,cpu,all]</term>
+		<term><option>--separate=</option>[none,lib,kernel,thread,cpu,all]</term>
 		<listitem><para>
 		By default, every profile is stored in a single file. Thus, for example,
 		samples in the C library are all accredited to the \
<filename>/lib/libc.o</filename> @@ -588,7 +588,7 @@ is required. These settings are \
stored i  <tgroup cols='2'> 
 		<tbody>
 		<row><entry><option>none</option></entry><entry>No profile separation \
                (default)</entry></row>
-		<row><entry><option>library</option></entry><entry>Create per-application profiles \
for libraries</entry></row> +		<row><entry><option>lib</option></entry><entry>Create \
per-application profiles for libraries</entry></row>  \
<row><entry><option>kernel</option></entry><entry>Create per-application profiles for \
the kernel and kernel modules</entry></row>  \
<row><entry><option>thread</option></entry><entry>Create profiles for each thread and \
each task</entry></row>  <row><entry><option>cpu</option></entry><entry>Create \
profiles for each CPU</entry></row> @@ -597,7 +597,7 @@ is required. These settings \
are stored i  </tgroup>
 		</informaltable>
 		<para>
-		Note  that <option>--separate=kernel</option> also turns on \
<option>--separate=library</option>. +		Note  that <option>--separate=kernel</option> \
also turns on <option>--separate=lib</option>.  <!-- FIXME: update if this change -->
 		When using <option>--separate=kernel</option>, samples in hardware interrupts, \
soft-irqs, or other  asynchronous kernel contexts are credited to the task currently \
running. This means you will see @@ -630,7 +630,7 @@ is required. These settings are \
stored i  binary images. This is useful for restricting the sometimes voluminous
 		output you may get otherwise, especially with
 		<option>--separate=thread</option>. Note that if you are using
-		<option>--separate=library</option> or
+		<option>--separate=lib</option> or
 		<option>--separate=kernel</option>, then if you specification an
 		application binary, the shared libraries and kernel code
 		<emphasis>are</emphasis> included. Specify the value
@@ -1383,16 +1383,6 @@ escaping is necessary as <option>image:<
 </screen>
 
 <para>
-Get a symbol summary if you have the actual profile file and binary
-(perhaps somebody has sent you them via e-mail). These parameters
-cannot be used in combination with any others as the default searches
-are not performed.
-</para>
-<screen>
-# opreport -l binary:./mybinary sample-file:./CPU_CLK_UNHALTED.231500.0.all.all.all
-</screen>
-
-<para>
 Image summaries for all binaries in the <filename>test</filename> directory,
 excepting <filename>boring-test</filename> :
 </para>
@@ -1493,22 +1483,6 @@ excepting <filename>boring-test</filenam
 	</varlistentry>
 
 	<varlistentry>
-		<term><option>binary:</option><emphasis>file</emphasis></term>
-		<listitem><para>
-		Give results only for the given file. This can only be used with
-		<option>sample-file:</option>.
-		</para></listitem>
-	</varlistentry>
-
-	<varlistentry>
-		<term><option>sample-file:</option><emphasis>file</emphasis></term>
-		<listitem><para>
-		Give results only for the given sample file. This can only be used with
-		<option>binary:</option>.
-		</para></listitem>
-	</varlistentry>
-
-	<varlistentry>
 		<term><option>cpu:</option><emphasis>cpulist</emphasis></term>
 		<listitem><para>
 		Only consider profiles for the given numbered CPU (starting from zero).
@@ -1593,7 +1567,7 @@ taken per second.
 Similarly, if the binary spends little time in the main binary image
 itself, with most of it spent in shared libraries it uses, you might
 not see any samples for the binary image itself. You can check this
-by using <command>opcontrol --separate=library</command> before the
+by using <command>opcontrol --separate=lib</command> before the
 profiling session, so <command>opreport</command> and friends show
 the library profiles on a per-application basis.
 </para></listitem></varlistentry>



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Oprofile-commits mailing list
Oprofile-commits@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oprofile-commits


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic