diff options
author | Bjoern Brandenburg <bbb@Serenity.local> | 2008-12-09 21:11:32 -0500 |
---|---|---|
committer | Bjoern Brandenburg <bbb@Serenity.local> | 2008-12-09 21:11:32 -0500 |
commit | d9d8a9b88c541484e8e8a91ad748ef065d2bce89 (patch) | |
tree | f5596527c8581cb4e60375356f10966c4781b428 | |
parent | e3494f4f6c1d05fcba62bcb4e34743791ec7813f (diff) |
fix headings
-rw-r--r-- | doc/tracing.html | 4 | ||||
-rw-r--r-- | doc/tracing.text | 8 |
2 files changed, 6 insertions, 6 deletions
diff --git a/doc/tracing.html b/doc/tracing.html index fb2dcce..c1a262b 100644 --- a/doc/tracing.html +++ b/doc/tracing.html | |||
@@ -156,7 +156,7 @@ Used to measure the time spent to enqueue a newly-released job in a ready queue. | |||
156 | 156 | ||
157 | <p>Once the recorded overheads have been exported to CSV files they can be easily analyzed with tools such as Python's <code>csv</code> module, Octave, or Matlab.</p> | 157 | <p>Once the recorded overheads have been exported to CSV files they can be easily analyzed with tools such as Python's <code>csv</code> module, Octave, or Matlab.</p> |
158 | 158 | ||
159 | <h2>Recording and Post-Processing Scheduling Traces</h2> | 159 | <h2>Recording Scheduling Traces</h2> |
160 | 160 | ||
161 | <p>Scheduling traces are also recorded using Feather-Trace. However, a different binary format is used. The definition and an explanation of the format can be found in the file <code>include/litmus/sched_trace.h</code> (in the kernel directory).</p> | 161 | <p>Scheduling traces are also recorded using Feather-Trace. However, a different binary format is used. The definition and an explanation of the format can be found in the file <code>include/litmus/sched_trace.h</code> (in the kernel directory).</p> |
162 | 162 | ||
@@ -185,7 +185,7 @@ Disabling 9 events. | |||
185 | 185 | ||
186 | <p><strong>Hint</strong>: The dummy real-time task <code>rtspin</code> (distributed as part of the <code>liblitmus</code> package) may be useful when studying/testing the behavior of a scheduler plugin.</p> | 186 | <p><strong>Hint</strong>: The dummy real-time task <code>rtspin</code> (distributed as part of the <code>liblitmus</code> package) may be useful when studying/testing the behavior of a scheduler plugin.</p> |
187 | 187 | ||
188 | <h2>Post-Processing Overhead Traces</h2> | 188 | <h2>Post-Processing Scheduling Traces</h2> |
189 | 189 | ||
190 | <p>The user space library and tools package <code>liblitmus</code> contains the necessary headers to write <code>sched_trace</code> post-processing and analysis tools (see <code>include/sched_trace.h</code> and <code>src/sched_trace.c</code>).</p> | 190 | <p>The user space library and tools package <code>liblitmus</code> contains the necessary headers to write <code>sched_trace</code> post-processing and analysis tools (see <code>include/sched_trace.h</code> and <code>src/sched_trace.c</code>).</p> |
191 | 191 | ||
diff --git a/doc/tracing.text b/doc/tracing.text index 1bdbac4..e91a758 100644 --- a/doc/tracing.text +++ b/doc/tracing.text | |||
@@ -142,8 +142,8 @@ For each event, the start time (in clock cycles) is given in the first column, t | |||
142 | 142 | ||
143 | Once the recorded overheads have been exported to CSV files they can be easily analyzed with tools such as Python's `csv` module, Octave, or Matlab. | 143 | Once the recorded overheads have been exported to CSV files they can be easily analyzed with tools such as Python's `csv` module, Octave, or Matlab. |
144 | 144 | ||
145 | Recording and Post-Processing Scheduling Traces | 145 | Recording Scheduling Traces |
146 | ----------------------------------------------- | 146 | --------------------------- |
147 | 147 | ||
148 | Scheduling traces are also recorded using Feather-Trace. However, a different binary format is used. The definition and an explanation of the format can be found in the file `include/litmus/sched_trace.h` (in the kernel directory). | 148 | Scheduling traces are also recorded using Feather-Trace. However, a different binary format is used. The definition and an explanation of the format can be found in the file `include/litmus/sched_trace.h` (in the kernel directory). |
149 | 149 | ||
@@ -171,8 +171,8 @@ Note that `st_trace` may have to be modified to change the default `sched_trace` | |||
171 | 171 | ||
172 | **Hint**: The dummy real-time task `rtspin` (distributed as part of the `liblitmus` package) may be useful when studying/testing the behavior of a scheduler plugin. | 172 | **Hint**: The dummy real-time task `rtspin` (distributed as part of the `liblitmus` package) may be useful when studying/testing the behavior of a scheduler plugin. |
173 | 173 | ||
174 | Post-Processing Overhead Traces | 174 | Post-Processing Scheduling Traces |
175 | ------------------------------- | 175 | --------------------------------- |
176 | 176 | ||
177 | The user space library and tools package `liblitmus` contains the necessary headers to write `sched_trace` post-processing and analysis tools (see `include/sched_trace.h` and `src/sched_trace.c`). | 177 | The user space library and tools package `liblitmus` contains the necessary headers to write `sched_trace` post-processing and analysis tools (see `include/sched_trace.h` and `src/sched_trace.c`). |
178 | 178 | ||