Lines Matching full:samples
76 Older versions of OProfile were not capable of attributing samples to symbols from dynamically
78 anonymous memory regions. OProfile reported the samples from such code, but the attribution
117 in profiling reports without any samples in these regions.
192 the oprofile daemon log when processing JIT samples if this special user
423 the profile data is written out into the $SESSION_DIR/samples directory (by default at <filename>/var/lib/oprofile/samples</filename>).
549 samples are taken. A counter can choose to sample only kernel code, user-space code,
658 Number of samples in kernel buffer. When using a 2.6 kernel
665 Set kernel buffer watershed to num samples (2.6 only). When it'll remain only
673 Number of samples in kernel per-cpu buffer (2.6 only). If you
696 samples in the C library are all accredited to the <filename>/lib/libc.o</filename>
715 When using <option>--separate=kernel</option>, samples in hardware interrupts, soft-irqs, or other
717 seemingly nonsense profiles such as <filename>/bin/bash</filename> showing samples for the PPP modules,
722 newly started kernel thread samples are credited to the vmlinux (kernel) profile.
771 to profile the kernel. This still counts the total number of kernel samples,
846 will create a sub-directory in <filename>$SESSION_DIR/samples</filename> containing the samples
851 <command>rm -rf $SESSION_DIR/samples/sessionname</command> or, for the
1088 back to using the real-time clock interrupt to collect samples. This interrupt is also used by the <command>rtc</command>
1155 (PMU) triggers sampling with maskable interrupts. Thus, samples will not occur
1184 results -- typically, zero (or near zero) samples in the generated report.
1227 when the report contains samples for just a single application, which is
1416 samples in the saved session called "stresstest" :
1581 Each session's sample files can be found in the $SESSION_DIR/samples/ directory (default: <filename>/var/lib/oprofile/samples/</filename>).
1621 get samples for short-running programs. You can help this by using a
1622 lower count for the performance counter, so there are a lot more samples
1628 not see any samples for the binary image itself. You can check this
1660 and symbol summaries. An image summary lists the number of samples for individual
1694 vma samples % image name symbol name
1785 samples % image name symbol name
1803 <function>strfry()</function>). The samples and percentage values here
1816 "[self]" marker. This records the normal samples for the function, but
1834 For all such code, the samples for the anonymously mapped code are stored in a samples subdirectory
1903 samples % diff % symbol name
1918 samples, and the percentage field represents the relative percentage of
1919 the symbol's samples in the second profile.
1929 sample value is the number of samples in the first profile; since we're
1954 samples taken in these regions; for example:
1959 samples % image name symbol name
1974 As shown in the opreport output above, OProfile is unable to attribute the samples to any
2076 number of samples, symbol name, debug filename and line number,
2084 of total samples.
2116 crediting source lines with samples not really "owned" by this line. Also see
2126 the original sources. Each line in the annotated source is prepended with the samples
2160 The first number on each line is the number of samples, whilst the second is
2161 the relative percentage of total samples.
2254 of total samples.
2270 <title>OProfile results with JIT samples</title>
2278 possible to map samples to the appropriate symbols.
2292 samples % image name symbol name
2342 Each sample counts as 1 samples.
2344 time samples samples calls T1/call T1/call name
2371 of total samples.
2452 The following command would convert the input samples files to the
2453 output samples files using the given abi file as a binary description
2564 The conclusion: don't trust samples coming at the end of a loop,
2566 samples
2578 Linux where interrupts are disabled, allowing collection of samples in virtually
2581 shadows", or blind spots: regions where no samples will be collected. Typically, the samples
2643 are taking samples at the very start (or the very end) of
2676 info does not give enough details for the if condition, so all samples are
2679 samples at an assembly level.
2690 samples at the very start and end of a function, where there is no apparent
2697 You may see that a function is credited with a certain number of samples, but
2730 Here, the function is credited with 1,882 samples, but the annotations
2734 such samples. In the case above, <function>memset</function> is the most
2740 following example it's trivially visible the sums of symbols samples is less
2741 than the number of the samples for this file. The difference must be accounted
2746 * Total samples for file : "arch/i386/kernel/process.c"
2758 The missing samples are not lost, they will be credited to another source
2762 samples for an inlined function.
2776 <!-- FIXME so what *actually* happens to those samples ? ignored ? -->
2843 So here it's clear that copying is correctly credited with of all the samples, but the
2902 Since OProfile samples are buffered and don′t have timing information, there is no way
2903 to correlate samples with the (possibly) varying address ranges in which the code for a symbol
2924 the second memory read is likely to have more samples.
