Lines Matching full:separate
608 Stop data collection (this separate step is not possible with 2.2 or 2.4 kernels).
693 <term><option>--separate=</option>[none,lib,kernel,thread,cpu,all]</term>
697 profile. However, you choose to create separate sample files by specifying
713 Note that <option>--separate=kernel</option> also turns on <option>--separate=lib</option>.
715 When using <option>--separate=kernel</option>, samples in hardware interrupts, soft-irqs, or other
725 Using <option>--separate=thread</option> creates a lot
753 <option>--separate=thread</option>. Note that if you are using
754 <option>--separate=lib</option> or
755 <option>--separate=kernel</option>, then if you specification an
821 <title>Separate profiles for libraries and the kernel</title>
827 # opcontrol --separate=kernel --vmlinux=/boot/2.6.0/vmlinux
1210 separation parameters (separate=cpu,lib) to ensure that sufficient information
1213 the performance of each separate SPU is not necessary.
1501 makes sense to use if you're using <option>--separate</option>.
1503 <option>--separate=kernel</option>.
1629 by using <command>opcontrol --separate=lib</command> before the
1687 <command>opcontrol --separate=kernel</command>, symbols from images that <command>oprofiled</command>
1713 <title>Merging separate profiles</title>
1715 If you have used one of the <option>--separate=</option> options
1716 whilst profiling, there can be several separate profiles for
1720 when using <option>--separate=lib</option>).
1969 even when using <option>--separate=none</option>.
1990 to separate the sample data across multiple events, cpus and threads. The XML
2031 used --separate.
2056 Merge any profiles separated in a --separate session.
2213 used --separate.
2415 used --separate.
