From: John Levon <movement@us...> - 2003-03-01 15:37:22
Update of /cvsroot/oprofile/oprofile/doc
In directory sc8-pr-cvs1:/tmp/cvs-serv7077/doc
Scale the default event count
RCS file: /cvsroot/oprofile/oprofile/doc/oprofile.xml,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -d -r1.51 -r1.52
--- oprofile.xml 1 Mar 2003 15:13:38 -0000 1.51
+++ oprofile.xml 1 Mar 2003 15:37:18 -0000 1.52
@@ -333,6 +333,7 @@
Note that OProfile will pick a default event for you, if OProfile is using the hardware performance counters.
The event chosen roughly corresponds to measuring CPU time spent in code.
@@ -374,21 +375,10 @@
Row::next(void) const[0x0813ac24]: 15.4904% (1352 samples)
-at the top. Note that over a longer run (or with a lower <option>ctr0-count</option> value) the number of samples will
-be much more statistically
-reliable. Note that these sample counts do <emphasis>not</emphasis> necessarily reflect the relative amounts of time
-spent in each function - it depends on the event being counted. In my case (on my CPU) OProfile used <constant>CPU_CLK_UNHALTED</constant>
-which the command <command>opcontrol --list-events</command> tells us is "clocks processor is not halted", so in fact is likely to represent
-the relative time spent accurately (in fact, experiments have shown that using this event is far more accurate than the values
-produced by <command>gprof</command>).
-If you're more used to <command>gprof</command> style profile output, you can use <command>oprofpp -g gmon.out</command> and then
-<command>gprof -p binary</command> to get flat profiles. OProfile does not (cannot) support the call graph
-feature of <command>gprof</command>.
+at the top. I could also have used <command>op_time</command> or <command>op_time -dnl</command> to
+get a summary of the entire system profile (try it !). When I'm done, I can shut down the
+profile with <command>opcontrol --shutdown</command>.