diff options
Diffstat (limited to 'doc/cpu_profiler.html')
| -rw-r--r-- | doc/cpu_profiler.html | 18 |
1 files changed, 4 insertions, 14 deletions
diff --git a/doc/cpu_profiler.html b/doc/cpu_profiler.html index ad0e9fd..bc18940 100644 --- a/doc/cpu_profiler.html +++ b/doc/cpu_profiler.html @@ -45,17 +45,13 @@ given run of an executable:</p> profile-filename as an argument. </ol> -<p>Profiling works correctly with threads. To use, just call -ProfilerRegisterThread() at the beginning of the routine the thread -runs. Profiling also works correctly with sub-processes: each child +<p>In Linux 2.6 and above, profiling works correctly with threads, +automatically profiling all threads. In Linux 2.4, profiling only +profiles the main thread (due to a kernel bug involving itimers and +threads). Profiling works correctly with sub-processes: each child process gets its own profile with its own name (generated by combining CPUPROFILE with the child's process id).</p> -<p>You can also turn profiling on and off throughout the code, and do -other tweaks. This functionality will not frequently be needed. See -/usr/local/include/google/profiler.h (or src/google/profiler.h in this -directory) for more details.</p> - <p>For security reasons, CPU profiling will not write to a file -- and is thus not usable -- for setuid programs.</p> @@ -68,12 +64,6 @@ profile.</p> <table frame=box rules=sides cellpadding=5 width=100%> <tr> -<td><code>PROFILESELECTED=1</code></td> - <td>If set, cpu-profiler will only profile regions of code - surrounded with - <code>ProfilerEnable()</code>/<code>ProfilerDisable()</code>. - </td> -</tr><tr> <td><code>PROFILEFREQUENCY=<i>x</i></code></td> <td>How many interrupts/second the cpu-profiler samples. </td> |