[e9a646]: docs / index.php3 Maximize Restore History

Download this file

index.php3    118 lines (95 with data), 3.8 kB

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
<?php require("../start_page.php"); start_page("docs/", "OProfile documentation"); ?>
<h2>Manuals</h2>
<p>
The manuals listed below are intended for three different audiences:
</p>
<ul>
<li>
<?php rlink("doc/index.html", "OProfile manual"); ?>, for all OProfile users
</li>
<li>
<?php rlink("doc/internals/index.html", "OProfile internals"); ?>, for OProfile contributors
and those who are curious about the inner workings of OProfile
</li>
<li>
<?php rlink("doc/devel/index.html", "OProfile JIT agent developer guide"); ?>, for OProfile-JIT agent
library developers wanting to extend the profiling capabilities to support new virtual
machines
</li>
</ul>
<h2>Example reports</h2>
<p>
You might want to see <?php rlink("examples/", "some example OProfile output"); ?>.
</p>
<h2>Cheat sheet</h2>
<p>
Your 4-step plan to profiling.
</p>
<ol>
<li>
Compile and install oprofile, making sure to use <tt>--with-linux</tt> option to point to
your current kernel source, or <tt>--with-kernel-support</tt> for 2.6 kernels.
</li>
<li>
Start up the profiler :
<div class="computeroutput"><?php rlink("doc/controlling.html", "opcontrol") ?> --vmlinux=/path/to/vmlinux
opcontrol --start
</div>
</li>
<li>
Now the profiler is running, go do what ever you want to profile.
</li>
<li>
Now let's generate a profile summary :
<div class="computeroutput"><?php rlink("doc/opreport.html#opreport-options", "opreport") ?> -l /path/to/mybinary
</div>
Or, if we built our binary with <tt>-g</tt>, we can produce some annotated source :
<div class="computeroutput"><?php rlink("doc/opannotate.html#opannotate-details", "opannotate") ?> --source --output-dir=/path/to/annotated-source /path/to/mybinary
</div>
Or we can look at the rankings of the various system components as a whole :
<div class="computeroutput">opreport
</div>
</li>
</ol>
<p>
If you reinstall Oprofile over a previous version you need, before starting the profiler, to:
<div class="computeroutput">opcontrol --reset
</div>
</p>
<h2>Event type reference</h2>
<p>
Quick reference for the available event types for the performance counters. The same
info can be retrieved by running <tt>op_help</tt>.
<br />
<?php
$doc_name = array(
"docs/alpha-ev4-events.php" => "ALPHA EV4 (kernel 2.6 only)",
"docs/alpha-ev5-events.php" => "ALPHA EV5 (kernel 2.6 only)",
"docs/alpha-ev6-events.php" => "ALPHA EV6 (kernel 2.6 only)",
"docs/alpha-ev67-events.php" => "ALPHA EV67 (kernel 2.6 only)",
"docs/amd-athlon-events.php" => "AMD Athlon/Duron",
"docs/amd-hammer-events.php" => "AMD64 processors",
"docs/arm-xscale-pmu1-events.php" => "ARM/XScale PMU1 (kernel >= 2.6.8 only)",
"docs/arm-xscale-pmu2-events.php" => "ARM/XScale PMU2 (kernel >= 2.6.8 only)",
"docs/intel-ppro-events.php" => "Intel Pentium Pro",
"docs/intel-pii-events.php" => "Intel Pentium II",
"docs/intel-piii-events.php" => "Intel Pentium III",
"docs/intel-P4-events.php" => "Intel P4",
"docs/intel-P4-ht2-events.php" => "Intel P4 with hyperthreading (kernel 2.6 only)",
"docs/intel-p6-mobile-events.php" => "Intel pentium M (P6 core) (kernel >= 2.6.7 only)",
"docs/intel-ia64-events.php" => "Intel IA64 (kernel 2.4 only)",
"docs/intel-ia64-itanium-events.php" => "Intel IA64 Itanium (kernel 2.4 only)",
"docs/intel-ia64-itanium2-events.php" => "Intel IA64 Itanium2 (kernel 2.4 only)",
"docs/mips-rm9000-events.php" => "MIPS rm9000 (kernel >= 2.6.11)",
"docs/ppc-e500-events.php" => "ppc e500 (kernel >= 2.6.11 only)",
"docs/ppc64-power4-events.php" => "ppc64 POWER4 (kernel >= 2.6.9 only)",
"docs/ppc64-power5-events.php" => "ppc64 POWER5 (kernel >= 2.6.9 only)",
"docs/ppc64-970-events.php" => "ppc64 970 (kernel 2.6 only)",
);
foreach ($doc_name as $file => $text) {
rlink($file, $text);
printf("<br />");
}
?>
</p>
<?php require("$top/end_page.php"); end_page("docs/"); ?>