Lines Matching full:linkend
55 <listitem><para>need to profile dynamically compiled code of supported virtual machines (see <xref linkend="jitsupport"/>)</para></listitem>
91 For information on how to use OProfile's JIT support, see <xref linkend="setup-jit"/>.
286 <xref linkend="requirements"/>, "Required user account". This option
466 Used for controlling the OProfile data collection, discussed in <xref linkend="controlling" />.
473 Used by virtual machines (like the Java VM) to record information about JITed code being profiled. See <xref linkend="setup-jit" />.
481 <xref linkend="opreport" />.
490 debugging symbols. See <xref linkend="opannotate" />.
498 <command>gprof -p</command>. See <xref linkend="opgprof" />.
509 See <xref linkend="oparchive" />.
519 See <xref linkend="opimport" />.
682 See <xref linkend="eventspec" /> below.
949 (<xref linkend="install" />).
996 the sampling rate and other related parameters are explained in <xref linkend="controlling-daemon" />.
998 etc. The counter setup interface should be self-explanatory; <xref linkend="hardware-counters" /> and related
1021 you must use OProfile in RTC mode in 2.4 (see <xref linkend="rtc" />), or timer mode in 2.6 (see <xref linkend="timer" />).
1057 <xref linkend="interpreting" /> and also in the Digital paper "ProfileMe: A Hardware Performance Counter".
1827 linkend="interpreting-callgraph" /> for an explanation.
1978 JITed code, see <xref linkend="getting-jit-reports" />.
1980 <para>For more information about JIT support in OProfile, see <xref linkend="jitsupport"/>.
2113 Note that for the reason explained in <xref linkend="hardware-counters" /> the results can be
2117 <xref linkend="interpreting" />.
2320 was reused during the sample session (see <xref linkend="overlapping-symbols" />).
