inline a function called once

[simgrid.git] / doc / doxygen / tracing.doc

diff --git a/doc/doxygen/tracing.doc b/doc/doxygen/tracing.doc
index 2c4a4d8..7c11bda 100644 (file)
--- a/doc/doxygen/tracing.doc
+++ b/doc/doxygen/tracing.doc
@@ -143,17 +143,6 @@ tracing/filename
 \endverbatim
   If you do not provide this parameter, the trace file will be named simgrid.trace.
 
 \endverbatim
   If you do not provide this parameter, the trace file will be named simgrid.trace.
 

-\li <b>\c
-tracing/onelink_only
-</b>:
-  By default, the tracing system uses all routes in the platform file
-  to re-create a "graph" of the platform and register it in the trace file.
-  This option let the user tell the tracing system to use only the routes
-  that are composed with just one link.
-\verbatim
---cfg=tracing/onelink_only:yes
-\endverbatim
-

 \li <b>\c
 tracing/smpi
 </b>:
 \li <b>\c
 tracing/smpi
 </b>:


@@ -201,6 +190,38 @@ exchanged in the trace, both in the links and on the states. For collective, siz
 --cfg=tracing/smpi/display_sizes:yes
 \endverbatim
 
 --cfg=tracing/smpi/display_sizes:yes
 \endverbatim
 

+\li <b>\c
+tracing/smpi/sleeping
+</b>:
+TODO
+\verbatim
+TODO
+\endverbatim
+
+\li <b>\c
+tracing/smpi/format
+</b>:
+TODO
+\verbatim
+TODO
+\endverbatim
+
+\li <b>\c
+tracing/smpi/format/ti_one_file
+</b>:
+TODO
+\verbatim
+TODO
+\endverbatim
+
+\li <b>\c
+tracing/msg/vm
+</b>:
+TODO
+\verbatim
+TODO
+\endverbatim
+

 \li <b>\c
 tracing/msg/process
 </b>:
 \li <b>\c
 tracing/msg/process
 </b>:


@@ -237,6 +258,22 @@ traced as usual.
 --cfg=tracing/onelink_only:yes
 \endverbatim
 
 --cfg=tracing/onelink_only:yes
 \endverbatim
 

+\li <b>\c
+tracing/disable_link
+</b>:
+TODO
+\verbatim
+TODO
+\endverbatim
+
+\li <b>\c
+tracing/disable_power
+</b>:
+TODO
+\verbatim
+TODO
+\endverbatim
+

 \li <b>\c
 tracing/disable_destroy
 </b>:
 \li <b>\c
 tracing/disable_destroy
 </b>:


@@ -274,6 +311,30 @@ Use this to add the contents of a file to the top of the trace file as comment.
 --cfg=tracing/comment_file:textual_file.txt
 \endverbatim
 
 --cfg=tracing/comment_file:textual_file.txt
 \endverbatim
 

+\li <b>\c
+tracing/precision
+</b>:
+TODO
+\verbatim
+TODO
+\endverbatim
+
+\li <b>\c
+tracing/platform
+</b>:
+TODO
+\verbatim
+TODO
+\endverbatim
+
+\li <b>\c
+tracing/platform/topology
+</b>:
+TODO
+\verbatim
+TODO
+\endverbatim
+

 \li <b>\c
 viva/categorized
 </b>:
 \li <b>\c
 viva/categorized
 </b>:


@@ -452,7 +513,7 @@ the beggining and size of the time slice.
 
 \subsubsection tracing_viva_graph Hierarchical Graph View
 
 
 \subsubsection tracing_viva_graph Hierarchical Graph View
 

-As stated above (see section \ref tracing_tracing_analyzing), one
+%As stated above (see section \ref tracing_tracing_analyzing), one

 possibility to analyze SimGrid traces is to use Viva's graph view with
 a graph configuration to customize the graph according to the
 traces. A valid graph configuration (we are using the non-XML <a
 possibility to analyze SimGrid traces is to use Viva's graph view with
 a graph configuration to customize the graph according to the
 traces. A valid graph configuration (we are using the non-XML <a