Lines Matching full:profiles
38 cache misses, or CPU cycles. OProfile provides profiles of code based on the number of these occurring events:
40 This information is aggregated into profiles for each binary image.</para>
59 <listitem><para>want instruction-level profiles</para></listitem>
60 <listitem><para>want call-graph profiles</para></listitem>
66 <listitem><para>require call graph profiles on platforms other than 2.6/x86</para></listitem>
68 <listitem><para>require 100% instruction-accurate profiles</para></listitem>
434 data across the entire system for all of these profiles, you can do :
543 by OProfile: functions and binaries at the top of the profiles reflect
704 <row><entry><option>lib</option></entry><entry>Create per-application profiles for libraries</entry></row>
705 <row><entry><option>kernel</option></entry><entry>Create per-application profiles for the kernel and kernel modules</entry></row>
706 <row><entry><option>thread</option></entry><entry>Create profiles for each thread and each task</entry></row>
707 <row><entry><option>cpu</option></entry><entry>Create profiles for each CPU</entry></row>
717 seemingly nonsense profiles such as <filename>/bin/bash</filename> showing samples for the PPP modules,
821 <title>Separate profiles for libraries and the kernel</title>
1053 you cannot rely on the profiles at the instruction level as being perfectly accurate.
1379 This is a set of definitions that describe which actual profiles should be
1405 define two profiles, giving differential output. This is done by
1415 Image summaries for all profiles with <constant>DATA_MEM_REFS</constant>
1547 Only consider profiles for the given numbered CPU (starting from zero).
1555 Only consider profiles for the given task groups. Unless some program
1566 Only consider profiles for the given threads. When using
1593 make sure to save the old binary if you need to do comparative profiles.
1631 the library profiles on a per-application basis.
1713 <title>Merging separate profiles</title>
1716 whilst profiling, there can be several separate profiles for
1866 <title>Differential profiles with <command>opreport</command></title>
1869 Often, we'd like to be able to compare two profiles. For example, when
1873 identifies two different profiles. The general form is of:
1884 For each of the profiles, the shared section is prefixed, and then the
1914 the profiles we're diffing.
1936 When comparing profiles between different binaries, it should be clear
1941 means that trying to compare library profiles between two different
2056 Merge any profiles separated in a --separate session.
2599 OProfile profiles kernel modules by default. However, there are a couple of problems
2625 <title>Interpreting call-graph profiles</title>
2627 Sometimes the results from call-graph profiles may be different to what
