2 files changed, 2 insertions, 2 deletions
diff --git a/doc/tracing.html b/doc/tracing.html
index 8640d3f..6a54b62 100644
--- a/doc/tracing.html
+++ b/doc/tracing.html
@@ -43,7 +43,7 @@ This document is part of the documentation of the <a href="../index.html">LITMUS
 <li><p><code>litmus_log</code>: This trace contains text messages (created with the <code>TRACE()</code>
 macro, see <code>litmus.h</code>) that convey information useful for debugging. There is one global
 <code>litmus_log</code> buffer for the whole system. The <code>litmus_log</code> facility is essentially a replacement for <code>printk()</code>, which cannot be invoked from scheduling code without risking deadlock. Debug tracing must be enabled at compile time. Note that debug tracing creates significant overhead because string formatting takes place. </p></li>
-<li><p><code>ft_trace</code>: This trace contains binary-encoded time stamps. It is used for overhead tracing. There is one global <code>ft_trace</code> buffer for the whole system. The "ft" stands for <a href="http://www.cs.unc.edu/~bbb/feather-trace">Feather-Trace</a>. Feather-Trace is designed to create only negligible overhead when event sources are disabled, and to incur only low overhead when recording time stamps.</p></li>
+<li><p><code>ft_trace</code>: This trace contains binary-encoded time stamps. It is used for overhead tracing. There is one global <code>ft_trace</code> buffer for the whole system. The "ft" stands for <a href="http://www.cs.unc.edu/~bbb/feathertrace">Feather-Trace</a>. Feather-Trace is designed to create only negligible overhead when event sources are disabled, and to incur only low overhead when recording time stamps.</p></li>
 <li><p><code>sched_trace</code>: This trace contains binary-encoded scheduling event information, <em>e.g.</em>, an event can be recorded whenever a task got scheduled, a job was released, a job completed, etc. There is one <code>sched_trace</code> buffer per processor. <code>sched_trace</code> is based on Feather-Trace and hence also incurs only negligible overhead when event sources are disabled.</p></li>
 </ol>
diff --git a/doc/tracing.txt b/doc/tracing.txt
index 7efcffd..80d14b0 100644
--- a/doc/tracing.txt
+++ b/doc/tracing.txt
@@ -34,7 +34,7 @@ As of version 2010.2, there are three tracing mechanisms available in LITMUS<sup
 macro, see `litmus.h`) that convey information useful for debugging. There is one global
 `litmus_log` buffer for the whole system. The `litmus_log` facility is essentially a replacement for `printk()`, which cannot be invoked from scheduling code without risking deadlock. Debug tracing must be enabled at compile time. Note that debug tracing creates significant overhead because string formatting takes place. 
-2. `ft_trace`: This trace contains binary-encoded time stamps. It is used for overhead tracing. There is one global `ft_trace` buffer for the whole system. The "ft" stands for [Feather-Trace](http://www.cs.unc.edu/~bbb/feather-trace). Feather-Trace is designed to create only negligible overhead when event sources are disabled, and to incur only low overhead when recording time stamps.
+2. `ft_trace`: This trace contains binary-encoded time stamps. It is used for overhead tracing. There is one global `ft_trace` buffer for the whole system. The "ft" stands for [Feather-Trace](http://www.cs.unc.edu/~bbb/feathertrace). Feather-Trace is designed to create only negligible overhead when event sources are disabled, and to incur only low overhead when recording time stamps.
 3. `sched_trace`: This trace contains binary-encoded scheduling event information, *e.g.*, an event can be recorded whenever a task got scheduled, a job was released, a job completed, etc. There is one `sched_trace` buffer per processor. `sched_trace` is based on Feather-Trace and hence also incurs only negligible overhead when event sources are disabled.

diff --git a/doc/tracing.html b/doc/tracing.html index 8640d3f..6a54b62 100644 --- a/doc/tracing.html +++ b/doc/tracing.html
@@ -43,7 +43,7 @@ This document is part of the documentation of the <a href="../index.html">LITMUS
43	<li><p><code>litmus_log</code>: This trace contains text messages (created with the <code>TRACE()</code>	43	<li><p><code>litmus_log</code>: This trace contains text messages (created with the <code>TRACE()</code>
44	macro, see <code>litmus.h</code>) that convey information useful for debugging. There is one global	44	macro, see <code>litmus.h</code>) that convey information useful for debugging. There is one global
45	<code>litmus_log</code> buffer for the whole system. The <code>litmus_log</code> facility is essentially a replacement for <code>printk()</code>, which cannot be invoked from scheduling code without risking deadlock. Debug tracing must be enabled at compile time. Note that debug tracing creates significant overhead because string formatting takes place. </p></li>	45	<code>litmus_log</code> buffer for the whole system. The <code>litmus_log</code> facility is essentially a replacement for <code>printk()</code>, which cannot be invoked from scheduling code without risking deadlock. Debug tracing must be enabled at compile time. Note that debug tracing creates significant overhead because string formatting takes place. </p></li>
46	<li><p><code>ft_trace</code>: This trace contains binary-encoded time stamps. It is used for overhead tracing. There is one global <code>ft_trace</code> buffer for the whole system. The "ft" stands for <a href="http://www.cs.unc.edu/~bbb/feather-trace">Feather-Trace</a>. Feather-Trace is designed to create only negligible overhead when event sources are disabled, and to incur only low overhead when recording time stamps.</p></li>	46	<li><p><code>ft_trace</code>: This trace contains binary-encoded time stamps. It is used for overhead tracing. There is one global <code>ft_trace</code> buffer for the whole system. The "ft" stands for <a href="http://www.cs.unc.edu/~bbb/feathertrace">Feather-Trace</a>. Feather-Trace is designed to create only negligible overhead when event sources are disabled, and to incur only low overhead when recording time stamps.</p></li>
47	<li><p><code>sched_trace</code>: This trace contains binary-encoded scheduling event information, <em>e.g.</em>, an event can be recorded whenever a task got scheduled, a job was released, a job completed, etc. There is one <code>sched_trace</code> buffer per processor. <code>sched_trace</code> is based on Feather-Trace and hence also incurs only negligible overhead when event sources are disabled.</p></li>	47	<li><p><code>sched_trace</code>: This trace contains binary-encoded scheduling event information, <em>e.g.</em>, an event can be recorded whenever a task got scheduled, a job was released, a job completed, etc. There is one <code>sched_trace</code> buffer per processor. <code>sched_trace</code> is based on Feather-Trace and hence also incurs only negligible overhead when event sources are disabled.</p></li>
48	</ol>	48	</ol>
49		49


diff --git a/doc/tracing.txt b/doc/tracing.txt index 7efcffd..80d14b0 100644 --- a/doc/tracing.txt +++ b/doc/tracing.txt
@@ -34,7 +34,7 @@ As of version 2010.2, there are three tracing mechanisms available in LITMUS<sup
34	macro, see `litmus.h`) that convey information useful for debugging. There is one global	34	macro, see `litmus.h`) that convey information useful for debugging. There is one global
35	`litmus_log` buffer for the whole system. The `litmus_log` facility is essentially a replacement for `printk()`, which cannot be invoked from scheduling code without risking deadlock. Debug tracing must be enabled at compile time. Note that debug tracing creates significant overhead because string formatting takes place.	35	`litmus_log` buffer for the whole system. The `litmus_log` facility is essentially a replacement for `printk()`, which cannot be invoked from scheduling code without risking deadlock. Debug tracing must be enabled at compile time. Note that debug tracing creates significant overhead because string formatting takes place.
36		36
37	2. `ft_trace`: This trace contains binary-encoded time stamps. It is used for overhead tracing. There is one global `ft_trace` buffer for the whole system. The "ft" stands for [Feather-Trace](http://www.cs.unc.edu/~bbb/feather-trace). Feather-Trace is designed to create only negligible overhead when event sources are disabled, and to incur only low overhead when recording time stamps.	37	2. `ft_trace`: This trace contains binary-encoded time stamps. It is used for overhead tracing. There is one global `ft_trace` buffer for the whole system. The "ft" stands for [Feather-Trace](http://www.cs.unc.edu/~bbb/feathertrace). Feather-Trace is designed to create only negligible overhead when event sources are disabled, and to incur only low overhead when recording time stamps.
38		38
39	3. `sched_trace`: This trace contains binary-encoded scheduling event information, e.g., an event can be recorded whenever a task got scheduled, a job was released, a job completed, etc. There is one `sched_trace` buffer per processor. `sched_trace` is based on Feather-Trace and hence also incurs only negligible overhead when event sources are disabled.	39	3. `sched_trace`: This trace contains binary-encoded scheduling event information, e.g., an event can be recorded whenever a task got scheduled, a job was released, a job completed, etc. There is one `sched_trace` buffer per processor. `sched_trace` is based on Feather-Trace and hence also incurs only negligible overhead when event sources are disabled.
40		40