From: John L. <mov...@us...> - 2003-03-01 14:20:13
|
Update of /cvsroot/oprofile/oprofile/doc In directory sc8-pr-cvs1:/tmp/cvs-serv27175/doc Modified Files: oprofile.xml Log Message: small fixes Index: oprofile.xml =================================================================== RCS file: /cvsroot/oprofile/oprofile/doc/oprofile.xml,v retrieving revision 1.49 retrieving revision 1.50 diff -u -d -r1.49 -r1.50 --- oprofile.xml 27 Feb 2003 20:23:33 -0000 1.49 +++ oprofile.xml 1 Mar 2003 14:20:07 -0000 1.50 @@ -33,6 +33,13 @@ to binaries. It runs transparently in the background collecting information at a low overhead. These features make it ideal for profiling entire systems to determine bottle necks in real-world systems. </para> +<para> +Many CPUs provide "performance counters", hardware registers that can count "events"; for example, +cache misses, or CPU cycles. OProfile provides access to these counters, so they may be used to +provide profiles of code based on the number of these occurring events. Some hardware setups do +not allow OProfile to use performance counters: in these cases, no events are available, and +OProfile operates in timer/RTC mode, as described in later chapters. +</para> <sect1 id="requirements"> <title>System requirements</title> @@ -218,6 +225,10 @@ 2.5 kernels or higher, you do not need kernel source, as long as the OProfile driver is enabled; additionally, you should not need to disable power management. +</para> +<para> +Please note that you must save or have available the <filename>vmlinux</filename> file +generated during a kernel compile, as OProfile needs it. </para> </sect1> |